Apache Install Error
I am getting what I think is an error message that is safely ignorable, but wish to report it. Only my recent Cygwin update I received the following error from post install processing. "Package: Unknown package apache2-mod_perl.sh exit code 127" -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
On 12/12/2013 10:13 AM, William M. (Mike) Miller wrote: I'm running Windows 8.1 (cygcheck.out attached) and did a Windows update this morning. Since then I cannot run emacs-X11. Sometimes the message is: Memory exhausted--use M-x save-some-buffers then exit and restart Emacs Often there is no message. Once I got: ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes (alignment: 2048): Cannot allocate memory Fatal error 6: AbortedAbort (core dumped) There was a previous report of this problem from last October (see http://cygwin.com/ml/cygwin/2013-10/msg00149.html), but there was no resolution in that thread. emacs-w32 runs without problems, and that's an acceptable workaround for me at the moment, so this isn't an urgent issue for me currently. I'll be appreciative of any insights, however. Does the problem occur with "emacs -Q"? Have you checked http://cygwin.com/faq/faq.html#faq.using.bloda ? Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
On Thu, Dec 12, 2013 at 11:04 AM, Ken Brown wrote: > On 12/12/2013 10:13 AM, William M. (Mike) Miller wrote: >> >> I'm running Windows 8.1 (cygcheck.out attached) and did a Windows >> update this morning. Since then I cannot run emacs-X11. Sometimes >> the message is: >> >> Memory exhausted--use M-x save-some-buffers then exit and restart Emacs >> >> Often there is no message. Once I got: >> >> ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes >> (alignment: 2048): Cannot allocate memory >> >> Fatal error 6: AbortedAbort (core dumped) > Does the problem occur with "emacs -Q"? Yes. > Have you checked http://cygwin.com/faq/faq.html#faq.using.bloda ? I hadn't previously. The only thing on that list that I run, to the best of my knowledge, is Windows Defender. I turned off real-time checking and tried emacs-X11 again, with the same result (a "Memory exhausted" error). -- William M. (Mike) Miller | Edison Design Group william.m.mil...@gmail.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
On 12/12/2013 11:17 AM, William M. (Mike) Miller wrote: On Thu, Dec 12, 2013 at 11:04 AM, Ken Brown wrote: On 12/12/2013 10:13 AM, William M. (Mike) Miller wrote: I'm running Windows 8.1 (cygcheck.out attached) and did a Windows update this morning. Since then I cannot run emacs-X11. Sometimes the message is: Memory exhausted--use M-x save-some-buffers then exit and restart Emacs Often there is no message. Once I got: ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes (alignment: 2048): Cannot allocate memory Fatal error 6: AbortedAbort (core dumped) Does the problem occur with "emacs -Q"? Yes. Have you checked http://cygwin.com/faq/faq.html#faq.using.bloda ? I hadn't previously. The only thing on that list that I run, to the best of my knowledge, is Windows Defender. I turned off real-time checking and tried emacs-X11 again, with the same result (a "Memory exhausted" error). I'm not sure turning off real-time protection is enough. Can you actually disable Windows Defender completely? Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
Ken Brown writes: >> ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes >> (alignment: 2048): Cannot allocate memory I'm seeing the same thing on Win7/64 Pro, both for 64bit and 32bit Cygwin. Since I don't normally use the X11 Emacs, unfortunately I don't know which update was introducing this, it used to worked OK a few weeks ago. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
On 12/12/2013 11:41 AM, Achim Gratz wrote: Ken Brown writes: ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes (alignment: 2048): Cannot allocate memory I'm seeing the same thing on Win7/64 Pro, both for 64bit and 32bit Cygwin. Since I don't normally use the X11 Emacs, unfortunately I don't know which update was introducing this, it used to worked OK a few weeks ago. And do you also use Windows Defender? If this isn't BLODA, I'm completely stumped. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
On Thu, Dec 12, 2013 at 11:29 AM, Ken Brown wrote: > On 12/12/2013 11:17 AM, William M. (Mike) Miller wrote: >> >> On Thu, Dec 12, 2013 at 11:04 AM, Ken Brown wrote: >>> >>> On 12/12/2013 10:13 AM, William M. (Mike) Miller wrote: I'm running Windows 8.1 (cygcheck.out attached) and did a Windows update this morning. Since then I cannot run emacs-X11. Sometimes the message is: Memory exhausted--use M-x save-some-buffers then exit and restart Emacs Often there is no message. Once I got: ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes (alignment: 2048): Cannot allocate memory Fatal error 6: AbortedAbort (core dumped) >>> Have you checked http://cygwin.com/faq/faq.html#faq.using.bloda ? >> >> I hadn't previously. The only thing on that list that I run, to the >> best of my knowledge, is Windows Defender. I turned off real-time >> checking and tried emacs-X11 again, with the same result (a "Memory >> exhausted" error). > > I'm not sure turning off real-time protection is enough. Can you actually > disable Windows Defender completely? Assuming that clearing the "Use this program" check box in the Administrator tab of Windows Defender "disables [it] completely," I just tried that, and it also made no difference. -- William M. (Mike) Miller | Edison Design Group william.m.mil...@gmail.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
On 12/12/2013 12:38 PM, William M. (Mike) Miller wrote: On Thu, Dec 12, 2013 at 11:29 AM, Ken Brown wrote: On 12/12/2013 11:17 AM, William M. (Mike) Miller wrote: On Thu, Dec 12, 2013 at 11:04 AM, Ken Brown wrote: On 12/12/2013 10:13 AM, William M. (Mike) Miller wrote: I'm running Windows 8.1 (cygcheck.out attached) and did a Windows update this morning. Since then I cannot run emacs-X11. Sometimes the message is: Memory exhausted--use M-x save-some-buffers then exit and restart Emacs Often there is no message. Once I got: ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes (alignment: 2048): Cannot allocate memory Fatal error 6: AbortedAbort (core dumped) Have you checked http://cygwin.com/faq/faq.html#faq.using.bloda ? I hadn't previously. The only thing on that list that I run, to the best of my knowledge, is Windows Defender. I turned off real-time checking and tried emacs-X11 again, with the same result (a "Memory exhausted" error). I'm not sure turning off real-time protection is enough. Can you actually disable Windows Defender completely? Assuming that clearing the "Use this program" check box in the Administrator tab of Windows Defender "disables [it] completely," I just tried that, and it also made no difference. Can you check the windows update history to see if anything there looks suspicious? Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
On Thu, Dec 12, 2013 at 12:13:34PM -0500, Ken Brown wrote: >On 12/12/2013 11:41 AM, Achim Gratz wrote: >> Ken Brown writes: ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes (alignment: 2048): Cannot allocate memory >> >> I'm seeing the same thing on Win7/64 Pro, both for 64bit and 32bit >> Cygwin. Since I don't normally use the X11 Emacs, unfortunately I don't >> know which update was introducing this, it used to worked OK a few weeks >> ago. > >And do you also use Windows Defender? > >If this isn't BLODA, I'm completely stumped. Would running under strace help? cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
On 12/12/2013 1:25 PM, Christopher Faylor wrote: On Thu, Dec 12, 2013 at 12:13:34PM -0500, Ken Brown wrote: On 12/12/2013 11:41 AM, Achim Gratz wrote: Ken Brown writes: ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes (alignment: 2048): Cannot allocate memory I'm seeing the same thing on Win7/64 Pro, both for 64bit and 32bit Cygwin. Since I don't normally use the X11 Emacs, unfortunately I don't know which update was introducing this, it used to worked OK a few weeks ago. And do you also use Windows Defender? If this isn't BLODA, I'm completely stumped. Would running under strace help? It might. Achim or Mike (or anyone who can reproduce this problem), could you run "strace -o strace.out emacs-X11 -Q" and post strace.out somewhere? Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
On Thu, Dec 12, 2013 at 02:45:27PM -0500, Ken Brown wrote: >On 12/12/2013 1:25 PM, Christopher Faylor wrote: >> On Thu, Dec 12, 2013 at 12:13:34PM -0500, Ken Brown wrote: >>> On 12/12/2013 11:41 AM, Achim Gratz wrote: Ken Brown writes: >> ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes >> (alignment: 2048): Cannot allocate memory I'm seeing the same thing on Win7/64 Pro, both for 64bit and 32bit Cygwin. Since I don't normally use the X11 Emacs, unfortunately I don't know which update was introducing this, it used to worked OK a few weeks ago. >>> >>> And do you also use Windows Defender? >>> >>> If this isn't BLODA, I'm completely stumped. >> >> Would running under strace help? > >It might. Achim or Mike (or anyone who can reproduce this problem), >could you run "strace -o strace.out emacs-X11 -Q" and post strace.out >somewhere? Btw, posting it somewhere is a good suggestion since strace output seems to be giving spamassassin some problems lately, making it hard to send here. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Fwd: Fwd: emacs-X11 memory problem after Windows update
On Thu, Dec 12, 2013 at 2:54 PM, Christopher Faylor wrote: > On Thu, Dec 12, 2013 at 02:45:27PM -0500, Ken Brown wrote: >>On 12/12/2013 1:25 PM, Christopher Faylor wrote: >>> On Thu, Dec 12, 2013 at 12:13:34PM -0500, Ken Brown wrote: On 12/12/2013 11:41 AM, Achim Gratz wrote: > Ken Brown writes: >>> ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes >>> (alignment: 2048): Cannot allocate memory > > I'm seeing the same thing on Win7/64 Pro, both for 64bit and 32bit > Cygwin. Since I don't normally use the X11 Emacs, unfortunately I don't > know which update was introducing this, it used to worked OK a few weeks > ago. And do you also use Windows Defender? If this isn't BLODA, I'm completely stumped. >>> >>> Would running under strace help? >> >>It might. Achim or Mike (or anyone who can reproduce this problem), >>could you run "strace -o strace.out emacs-X11 -Q" and post strace.out >>somewhere? > > Btw, posting it somewhere is a good suggestion since strace output seems > to be giving spamassassin some problems lately, making it hard to send > here. Okay, here it is: https://drive.google.com/file/d/0B5QasYpFDUHeWGdsQ0RlWkk5Wm8/edit?usp=sharing I was watching this in Task Manager; the emacs-X11 process got up to around 400+ MB before dying with a segfault. BTW, I am beginning to think that the link with Windows Update is a red herring; I uninstalled all the updates from this morning, one by one, and emacs-X11 still failed. I then rolled back to a restore point from a couple of days ago, again to no effect. I don't know what changed, though; everything was working fine until this morning. -- William M. (Mike) Miller | Edison Design Group william.m.mil...@gmail.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: emacs-X11 memory problem after Windows update
Ken Brown writes: > And do you also use Windows Defender? MSE (which I believe is just the "consumer" name for the same software). > If this isn't BLODA, I'm completely stumped. So far I've not had persistent problems with MSE (doesn't mean anything really… I know). Only when an application is newly installed you can get some more interference, but that usually goes away after the application has been run the first few times (or after running a full scan, which is awfully slow). The crash in 64bit is not very reproducible and I haven't been able to get it segfault in gdb, so there _is_ some racing involved I guess. On 32bit however it reproduces under gdb sometimes, but not always: --8<---cut here---start->8--- Reading symbols from /usr/bin/emacs-X11...Reading symbols from /usr/lib/debug/usr/bin/emacs-X11.exe.dbg...done. done. (gdb) run Starting program: /usr/bin/emacs-X11 [New Thread 6260.0x1c74] [New Thread 6260.0x2348] [New Thread 6260.0x20fc] [New Thread 6260.0x1ccc] [New Thread 6260.0x20d8] [New Thread 6260.0x1f9c] [New Thread 6260.0x2380] Program received signal SIGSEGV, Segmentation fault. _malloc_internal_nolock (size=, size@entry=4) at /usr/src/debug/emacs-24.3-2/src/gmalloc.c:744 744 next->next->prev = next->prev; (gdb) thr aplly all bt No symbol "aplly" in current context. (gdb) thr app all bt Thread 7 (Thread 6260.0x2380): #0 0x77ccf8d1 in ntdll!ZwWaitForSingleObject () from /cygdrive/c/windows/system32/ntdll.dll #1 0x77ccf8d1 in ntdll!ZwWaitForSingleObject () from /cygdrive/c/windows/system32/ntdll.dll #2 0x76c7149d in WaitForSingleObjectEx () from /cygdrive/c/windows/syswow64/KERNELBASE.dll #3 0x048c in ?? () #4 0x in ?? () Thread 6 (Thread 6260.0x1f9c): #0 0x77ccf8d1 in ntdll!ZwWaitForSingleObject () from /cygdrive/c/windows/system32/ntdll.dll #1 0x77ccf8d1 in ntdll!ZwWaitForSingleObject () from /cygdrive/c/windows/system32/ntdll.dll #2 0x76c7149d in WaitForSingleObjectEx () from /cygdrive/c/windows/syswow64/KERNELBASE.dll #3 0x0344 in ?? () #4 0x in ?? () Thread 5 (Thread 6260.0x20d8): #0 0x77ccf959 in ntdll!ZwRemoveIoCompletion () from /cygdrive/c/windows/system32/ntdll.dll #1 0x77ccf959 in ntdll!ZwRemoveIoCompletion () from /cygdrive/c/windows/system32/ntdll.dll #2 0x71da635c in ?? () from /cygdrive/c/windows/SysWOW64/mswsock.dll #3 0x61005c5f in _cygtls::call2(unsigned long (*)(void*, void*), void*, void*)@16 (this=, func=0x0, arg=0x159d1a0, buf=0x3b9cdc4) at /usr/src/debug/cygwin-1.7.27-2/winsup/cygwin/cygtls.cc:100 #4 0x03b9cdc4 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 4 (Thread 6260.0x1ccc): #0 0x77ccf8d1 in ntdll!ZwWaitForSingleObject () from /cygdrive/c/windows/system32/ntdll.dll #1 0x77ccf8d1 in ntdll!ZwWaitForSingleObject () from /cygdrive/c/windows/system32/ntdll.dll #2 0x76c7149d in WaitForSingleObjectEx () from /cygdrive/c/windows/syswow64/KERNELBASE.dll #3 0x02e0 in ?? () #4 0x in ?? () Thread 3 (Thread 6260.0x20fc): #0 0x77cd015d in ntdll!ZwWaitForMultipleObjects () from /cygdrive/c/windows/system32/ntdll.dll #1 0x77cd015d in ntdll!ZwWaitForMultipleObjects () from /cygdrive/c/windows/system32/ntdll.dll #2 0x77d02f91 in ntdll!RtlMoveMemory () from /cygdrive/c/windows/system32/ntdll.dll #3 0x0001 in ?? () #4 0x0001 in ?? () #5 0x in ?? () Thread 2 (Thread 6260.0x2348): #0 0x77ccf905 in ntdll!ZwReadFile () from /cygdrive/c/windows/system32/ntdll.dll #1 0x77ccf905 in ntdll!ZwReadFile () from /cygdrive/c/windows/system32/ntdll.dll #2 0x76c6dd54 in ReadFile () from /cygdrive/c/windows/syswow64/KERNELBASE.dll #3 0x0090 in ?? () #4 0x772f3ec7 in ReadFile () from /cygdrive/c/windows/syswow64/kernel32.dll #5 0x0090 in ?? () #6 0x610db6e8 in wait_sig () at /usr/src/debug/cygwin-1.7.27-2/winsup/cygwin/sigproc.cc:1214 #7 0x in ?? () Thread 1 (Thread 6260.0x1c74): #0 _malloc_internal_nolock (size=, size@entry=4) at /usr/src/debug/emacs-24.3-2/src/gmalloc.c:744 #1 0x00597478 in _realloc_internal_nolock (ptr=ptr@entry=0x88d98f80, size=size@entry=4) at /usr/src/debug/emacs-24.3-2/src/gmalloc.c:1432 #2 0x00597601 in _realloc_internal (ptr=0x88d98f80, size=4) at /usr/src/debug/emacs-24.3-2/src/gmalloc.c:1452 #3 0x61082cdd in realloc (p=0x88d98f80, size=4) at /usr/src/debug/cygwin-1.7.27-2/winsup/cygwin/malloc_wrapper.cc:73 #4 0x88d98f80 in ?? () #5 0x014e9c88 in _fraghead () #6 0x88d63b80 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) print next $1 = (struct list *) 0x88d886f0 (gdb) print next->prev $2 = (struct list *) 0x14e9c88 <_fraghead+40> --8<---cut here---end--->8--- IIRC I've had crashes like these (where GSlice complains about alignment) before on Linux when there was a mismatch between glib and some other library. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46
Re: Fwd: Fwd: emacs-X11 memory problem after Windows update
On 12/12/2013 3:42 PM, William M. (Mike) Miller wrote: On Thu, Dec 12, 2013 at 2:54 PM, Christopher Faylor wrote: On Thu, Dec 12, 2013 at 02:45:27PM -0500, Ken Brown wrote: On 12/12/2013 1:25 PM, Christopher Faylor wrote: On Thu, Dec 12, 2013 at 12:13:34PM -0500, Ken Brown wrote: On 12/12/2013 11:41 AM, Achim Gratz wrote: Ken Brown writes: ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes (alignment: 2048): Cannot allocate memory I'm seeing the same thing on Win7/64 Pro, both for 64bit and 32bit Cygwin. Since I don't normally use the X11 Emacs, unfortunately I don't know which update was introducing this, it used to worked OK a few weeks ago. And do you also use Windows Defender? If this isn't BLODA, I'm completely stumped. Would running under strace help? It might. Achim or Mike (or anyone who can reproduce this problem), could you run "strace -o strace.out emacs-X11 -Q" and post strace.out somewhere? Btw, posting it somewhere is a good suggestion since strace output seems to be giving spamassassin some problems lately, making it hard to send here. Okay, here it is: https://drive.google.com/file/d/0B5QasYpFDUHeWGdsQ0RlWkk5Wm8/edit?usp=sharing There's something weird going on with fonts. I'm not very good at interpreting strace output, but it looks like emacs is trying to read all the fonts on your system and running out of memory. I suggest that you delete the directories ~/.fontconfig and ~/.cache/fontconfig. Then run (as administrator) "fc-cache -fsv". See if that helps. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Are there any plans to add chere in the x64 version?
Is there a feature request filed and any link to it so I can follow? Thanx in advance. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: Fwd: emacs-X11 memory problem after Windows update
On Thu, Dec 12, 2013 at 5:20 PM, Ken Brown wrote: > On 12/12/2013 3:42 PM, William M. (Mike) Miller wrote: >> >> On Thu, Dec 12, 2013 at 2:54 PM, Christopher Faylor wrote: >>> >>> On Thu, Dec 12, 2013 at 02:45:27PM -0500, Ken Brown wrote: On 12/12/2013 1:25 PM, Christopher Faylor wrote: > > On Thu, Dec 12, 2013 at 12:13:34PM -0500, Ken Brown wrote: >> >> On 12/12/2013 11:41 AM, Achim Gratz wrote: >>> >>> Ken Brown writes: > > ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 > bytes > (alignment: 2048): Cannot allocate memory >>> >>> >>> I'm seeing the same thing on Win7/64 Pro, both for 64bit and 32bit >>> Cygwin. Since I don't normally use the X11 Emacs, unfortunately I >>> don't >>> know which update was introducing this, it used to worked OK a few >>> weeks >>> ago. >> >> >> And do you also use Windows Defender? >> >> If this isn't BLODA, I'm completely stumped. > > > Would running under strace help? It might. Achim or Mike (or anyone who can reproduce this problem), could you run "strace -o strace.out emacs-X11 -Q" and post strace.out somewhere? >>> >>> >>> Btw, posting it somewhere is a good suggestion since strace output seems >>> to be giving spamassassin some problems lately, making it hard to send >>> here. >> >> >> Okay, here it is: >> >> >> https://drive.google.com/file/d/0B5QasYpFDUHeWGdsQ0RlWkk5Wm8/edit?usp=sharing > > > There's something weird going on with fonts. I'm not very good at > interpreting strace output, but it looks like emacs is trying to read all > the fonts on your system and running out of memory. I suggest that you > delete the directories ~/.fontconfig and ~/.cache/fontconfig. Then run (as > administrator) "fc-cache -fsv". See if that helps. I did not have those directories in my home directory, but I ran the fc-cache command as you suggested, and that fixed the problem. Thanks! -- William M. (Mike) Miller | Edison Design Group william.m.mil...@gmail.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Are there any plans to add chere in the x64 version?
On 12/12/2013 17:01, klonos wrote: Is there a feature request filed and any link to it so I can follow? Thanx in advance. There's no feature request or link. I suspect the 32 bit package will work with x64 but haven't had time to check. Dave. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
chere does not add an entry in the context menu initiated within folders/drives (right clicking in an empty space while inside the folder/drive)
chere adds context menu entries for when right-clicking on folders (under HKCR\Directory\shell\) and local/removable/network drives (under HKCR\Drive\shell\) but it doesn't add an entry to the folder/drive background context menu (HKCR\Directory\Background\shell and HKCR\Drive\Background\shell\). Is this a known bug or by design? If by design and there is no intention to add that feature by default, could you then at least add a switch to allow that optionally? Thanx. PS: on another note, it would be nice if the context menu entries also had an icon. It helps a lot to spot the entry when the context menus are large. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: chere does not add an entry in the context menu initiated within folders/drives (right clicking in an empty space while inside the folder/drive)
On 12/12/13 17:49, klonos wrote: chere adds context menu entries for when right-clicking on folders (under HKCR\Directory\shell\) and local/removable/network drives (under HKCR\Drive\shell\) but it doesn't add an entry to the folder/drive background context menu (HKCR\Directory\Background\shell and HKCR\Drive\Background\shell\). Is this a known bug or by design? If by design and there is no intention to add that feature by default, could you then at least add a switch to allow that optionally? Thanx. I was not aware of the Drive\Background and Directory\Background keys. Presumably it's been added since I last looked. I've a feeling someone submitted a patch, but I haven't looked at updating chere for a while. I guess I should find some time to handle x64 and this. Dave. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: chere does not add an entry in the context menu initiated within folders/drives (right clicking in an empty space while inside the folder/drive)
On Thu, Dec 12, 2013 at 08:11:06PM -0800, David Kilroy wrote: >On 12/12/13 17:49, klonos wrote: >> chere adds context menu entries for when right-clicking on folders >> (under HKCR\Directory\shell\) and local/removable/network drives (under >> HKCR\Drive\shell\) but it doesn't add an entry to the folder/drive >> background context menu (HKCR\Directory\Background\shell and >> HKCR\Drive\Background\shell\). >> >> Is this a known bug or by design? If by design and there is no intention >> to add that feature by default, could you then at least add a switch to >> allow that optionally? Thanx. > >I was not aware of the Drive\Background and Directory\Background keys. >Presumably it's been added since I last looked. > >I've a feeling someone submitted a patch, but I haven't looked at >updating chere for a while. > >I guess I should find some time to handle x64 and this. Thanks. And once that is ready, don't forget to get yourself upload privileges so that you can upload your package yourself: https://sourceware.org/cygwin-apps/package-upload.html -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
