Re: Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3]
Ken Brown wrote: Would you mind sending me your cygcheck output Attached... What anti-virus software do you use (if any)? Microsoft Security Essential (MSE)... I would be glad if someone could teach me how do not use an AV on Windows... ;-) Ciao, Angelo. cygcheck.out.bz2 Description: Binary data -- 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: Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3]
On 4/7/2012 6:11 PM, Angelo Graziosi wrote: Il 06/04/2012 21.22, Angelo Graziosi ha scritto: Any way I will try to follow your recipe to reproduce the problem, but I am sure it is still there.. No, it isn't! I have run Emacs for more than 14 hours and I haven't see any problem. I have done that strictly following your recipe... Hi Angelo, That's great news. Thank you very much for testing. Now I just have to figure out why it doesn't work on my system. Would you mind sending me your cygcheck output off-list so I can see how my setup differs from yours? I wonder if I need some GNOME-related package. Or it could be BLODA. What anti-virus software do you use (if any)? Thanks. Ken -- 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: Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3]
Il 06/04/2012 21.22, Angelo Graziosi ha scritto: Any way I will try to follow your recipe to reproduce the problem, but I am sure it is still there.. No, it isn't! I have run Emacs for more than 14 hours and I haven't see any problem. I have done that strictly following your recipe... Ciao, Angelo. -- 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: Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3]
Hi Ken, Ken Brown wrote: Now I can reproduce the problem with both gtk2 and gtk3 If you remember I flagged this on 24.11.2011 with a private mail. After the upgrading to GNOME 3.2, not only the gtk3 build was unstable but also the old gtk2 builds were unstable... Since then I am using this target C:\cygwin-2\bin\run.exe bash -l -c 'GSETTINGS_BACKEND=memory emacs -display 127.0.0.1:0.0 2>/dev/null &' to start Emacs from a link on desktop, and it works both with gtk2 and with gtk3 builds. Notice, I do not use Cygwin service (dbus,... etc.) Any way I will try to follow your recipe to reproduce the problem, but I am sure it is still there.. Here are the steps for reproducing the problem: Ciao, Angelo. -- 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: Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3]
On 4/4/2012 6:12 PM, Yaakov (Cygwin/X) wrote:
On 2012-04-04 09:15, Ken Brown wrote:
Another option is to use gtk3 but to put the GSETTINGS_BACKEND
workaround into the emacs startup code:
setenv ("GSETTINGS_BACKEND", "memory", 1);
I've been testing this, and it seems to work (but I won't be completely
confident until I've had emacs running for a day or so). Do you see any
downside?
This is intended solely for testing and debugging. Settings will not be
saved from one invocation to the next, so that's a pretty big downside.
OK, that was a bad idea. I'm going to try to debug this problem.
I was wrong when I said that the problem doesn't occur with gtk2. I
based that statement on earlier tests; but I did those tests several
months ago, when I started this thread, and I probably didn't have
dconf-service installed at the time. Now I can reproduce the problem
with both gtk2 and gtk3. But the problem doesn't occur if I build emacs
with the configure option --without-gsettings. I've changed the subject
line accordingly.
By the way, emacs (starting with emacs-24) will use both GSettings and
GConf if they're available. But there doesn't appear to be any problem
using GConf alone.
Here's my most recent debugging session. This is from a build using
gtk2 and GSettings (but not GConf):
GNU gdb (GDB) 7.3.50.20111026-cvs (cygwin-special)
[...]
Reading symbols from /home/kbrown/src/emacs/test/src/emacs...done.
(gdb) r -Q
Starting program: /home/kbrown/src/emacs/test/src/emacs -Q
[New Thread 12220.0x950]
[...]
[New Thread 12220.0x330c]
Program received signal SIGSEGV, Segmentation fault.
0x00289d7a in ?? ()
(gdb) bt full
#0 0x00289d7a in ?? ()
No symbol table info available.
#1 0x007bd264 in __morecore ()
No symbol table info available.
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
#2 0x0001 in ?? ()
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
wsock_started = true
wsadata = {wVersion = 514, wHighVersion = 514,
szDescription = "WinSock 2.0", '\000' ,
szSystemStatus = "Running", '\000' ,
iMaxSockets = 0, iMaxUdpDg = 0, lpVendorInfo = 0x0}
#3 0x00606175 in calloc (nmemb=4294867296, size=8) at gmalloc.c:1547
result = 0x0
#4 0x in ?? ()
No symbol table info available.
This looks very strange to me, especially the part about WinSock. Where
could that have come from?
Here are the steps for reproducing the problem:
1. Install the following packages and their dependencies:
gnutls-devel
libdbus1-devel
libdbus1_3
libgif-devel
libgtk2.0-devel
libgtk3-devel
libMagick-devel
libMagickCore5
librsvg2-devel
libSM-devel
libXpm-devel
[These might not all be necessary for reproducing the problem, but
they're used in my build or as runtime dependencies of my build.]
2. Build emacs with GSettings support but not GConf support:
wget ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-24.0.95.tar.gz
tar -xf emacs-24.0.95.tar.gz
cd emacs-24.0.95
./configure --without-gconf && make
[Note: By default, the build will use gtk2. The option
"--with-x-toolkit=gtk3" will make it use gtk3.]
3. Start the X server using the Start Menu shortcut, with no ~/.startxwinrc.
4. In the resulting xterm window:
eval `dbus-launch --sh-syntax`
cd emacs-24.0.95/src
./emacs -Q &
5. Ignore emacs; it will eventually crash. This could take one or more
hours, but it happens every time on my system. It happens much faster
if I don't disable GConf support.
It would be extremely helpful if someone could try to reproduce this.
At the very least, I'd like to rule out the possibility that it's caused
by BLODA on my system.
Ken
--
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: Problems with emacs built against gtk3
On 2012-04-04 09:15, Ken Brown wrote:
Another option is to use gtk3 but to put the GSETTINGS_BACKEND
workaround into the emacs startup code:
setenv ("GSETTINGS_BACKEND", "memory", 1);
I've been testing this, and it seems to work (but I won't be completely
confident until I've had emacs running for a day or so). Do you see any
downside?
This is intended solely for testing and debugging. Settings will not be
saved from one invocation to the next, so that's a pretty big downside.
Yaakov
--
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: Problems with emacs built against gtk3
On 4/3/2012 11:55 PM, Yaakov (Cygwin/X) wrote:
On 2012-04-03 20:52, Ken Brown wrote:
There's no problem when emacs is built with gtk2. There's also no
problem with gtk3, provided I set GSETTINGS_BACKEND=memory.
I regularly run the entire GNOME desktop for hours (if not days) on end,
so I really don't think that this is a bug in dconf or gvfs.
I'll probably just have to stick with gtk2 for the next emacs release.
That's fine; gtk2 isn't going anywhere for a while.
Another option is to use gtk3 but to put the GSETTINGS_BACKEND
workaround into the emacs startup code:
setenv ("GSETTINGS_BACKEND", "memory", 1);
I've been testing this, and it seems to work (but I won't be completely
confident until I've had emacs running for a day or so). Do you see any
downside?
Ken
--
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: Problems with emacs built against gtk3
On 2012-04-03 20:52, Ken Brown wrote: There's no problem when emacs is built with gtk2. There's also no problem with gtk3, provided I set GSETTINGS_BACKEND=memory. I regularly run the entire GNOME desktop for hours (if not days) on end, so I really don't think that this is a bug in dconf or gvfs. I'll probably just have to stick with gtk2 for the next emacs release. That's fine; gtk2 isn't going anywhere for a while. Yaakov -- 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: Problems with emacs built against gtk3
On 4/3/2012 6:30 PM, Yaakov (Cygwin/X) wrote: On 2012-04-03 16:11, Ken Brown wrote: Now that gvfs is available, I've built the latest emacs-24 pretest against gtk3 and removed the GSETTINGS_BACKEND=memory setting, but I still have the same problem. If I start emacs and then just walk away from it, after a while it will die with a segfault. (It may take an hour or more before this happens.) And with gtk2? There's no problem when emacs is built with gtk2. There's also no problem with gtk3, provided I set GSETTINGS_BACKEND=memory. I'll probably just have to stick with gtk2 for the next emacs release. Ken -- 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: Problems with emacs built against gtk3
On 2012-04-03 16:11, Ken Brown wrote: Now that gvfs is available, I've built the latest emacs-24 pretest against gtk3 and removed the GSETTINGS_BACKEND=memory setting, but I still have the same problem. If I start emacs and then just walk away from it, after a while it will die with a segfault. (It may take an hour or more before this happens.) And with gtk2? I've got a backtrace (attached), but it may not be useful because of optimization. I don't see anything in the backtrace which indicates that this is gtk3-related; I would guess it is a bug in either cygwin or emacs. Yaakov -- 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: Problems with emacs built against gtk3
On 12/9/2011 8:39 PM, nyc4...@aol.com wrote: Ken Brown writes: On 11/30/2011 6:54 AM, Yaakov (Cygwin/X) wrote: On Wed, 2011-11-30 at 11:17 +0100, Pavel Holejsovsky wrote: On 11/30/2011 4:51 AM, Yaakov (Cygwin/X) wrote: 2. The pango warning can already be observed with the current Cygwin emacs after the recent update of the GNOME libraries. To reproduce, install the emacs-X11 package and start emacs with the command `emacs&' in an xterm window. I cannot reproduce this. Does installing font-cantarell-otf help? Perhaps another font? I can reproduce it, in fact almost every gtk-enabled application spits that out. I tried stracing, and I think (but I'm not sure) that the warning appears after pango tries to load /usr/lib/pango/1.6.0/modules/pango-basic-fc.dll -> there is no /usr/lib/pango directory on my system, and it seems that no package in cygwin or ports repository provides it. That's the clue I needed. I switched pango to builtin modules over a year ago in Ports to help minimize fork() errors, but that didn't reach the distro until now. If I'm right, removing /etc/pango/pango.modules should fix it. That fixes it. Thanks. Unless I do: GSETTINGS_BACKEND=memory emacs& I get the following error: $ (emacs:4048): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. ** (emacs:4048): WARNING **: Abnormal program termination spawning command line `dbus-launch --autolaunch=614770a5ea44ec425e4c57144ed14d5c --binary-syntax --close-stderr': [1]+ Segmentation fault emacs I have no /etc/pango/pango.modules file Removing /etc/pango/pango.modules was to get rid of a pango warning that a lot of people were getting. Yaakov explained how to get rid of the error you're talking about here: http://cygwin.com/ml/cygwin-xfree/2011-11/msg00045.html Ken -- 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: Problems with emacs built against gtk3
Ken Brown writes: > On 11/30/2011 6:54 AM, Yaakov (Cygwin/X) wrote: >> On Wed, 2011-11-30 at 11:17 +0100, Pavel Holejsovsky wrote: >>> On 11/30/2011 4:51 AM, Yaakov (Cygwin/X) wrote: > 2. The pango warning can already be observed with the current Cygwin > emacs after the recent update of the GNOME libraries. To reproduce, > install the emacs-X11 package and start emacs with the command `emacs&' > in an xterm window. I cannot reproduce this. Does installing font-cantarell-otf help? Perhaps another font? >>> >>> I can reproduce it, in fact almost every gtk-enabled application spits >>> that out. I tried stracing, and I think (but I'm not sure) that the >>> warning appears after pango tries to load >>> /usr/lib/pango/1.6.0/modules/pango-basic-fc.dll -> there is no >>> /usr/lib/pango directory on my system, and it seems that no package in >>> cygwin or ports repository provides it. >> >> That's the clue I needed. I switched pango to builtin modules over a >> year ago in Ports to help minimize fork() errors, but that didn't reach >> the distro until now. If I'm right, removing /etc/pango/pango.modules >> should fix it. > > That fixes it. Thanks. Unless I do: GSETTINGS_BACKEND=memory emacs& I get the following error: $ (emacs:4048): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. ** (emacs:4048): WARNING **: Abnormal program termination spawning command line `dbus-launch --autolaunch=614770a5ea44ec425e4c57144ed14d5c --binary-syntax --close-stderr': [1]+ Segmentation fault emacs I have no /etc/pango/pango.modules file > > Ken > > > -- > 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: Problems with emacs built against gtk3
On 12/4/2011 8:44 PM, Ken Brown wrote: On 12/4/2011 7:13 PM, Yaakov (Cygwin/X) wrote: On Fri, 2011-12-02 at 08:01 -0500, Ken Brown wrote: This doesn't do it. Emacs still dies after a short time. I don't know if that means that there's something else going on, but I'll retest it after you package gvfs. In the meantime, I'll continue with my workaround of setting GSETTINGS_BACKEND=memory. In case you (or anyone else) wants to experiment with this, you can get my build of the emacs-24 pretest by running setup.exe -K http://www.math.cornell.edu/~kbrown/kbrown.gpg and adding http://www.math.cornell.edu/~kbrown to the list of mirrors. WJFFM, but I'll get on that gvfs ITP right away. It looks like I also need to repackage pango1.0 to remove everyone's old pango.modules file. But despite your subject line, the binaries there are clearly gtk2 based. Was that intended? No, I made a mistake in my configure arguments. I put `--with-x=gtk3' instead of `--with-x-toolkit=gtk3', so emacs used the default gtk2. I'll rebuild it. I've rebuilt emacs and am now definitely using gtk3. I've also installed the latest Cygwin snapshot. I tried your suggested workaround again (export GIO_USE_VFS=local) and it still doesn't work for me, but the symptoms are different: emacs doesn't die, but it freezes as soon as I try to list a directory with the command `d'. [This runs `ls' in a subprocess.] I then went back to my GSETTINGS_BACKEND=memory workaround and noticed something new: If I run emacs in my normal way, with "emacs.geometry: 82x36+340+40" in .Xdefaults, I get the following error message: Gtk-WARNING **: gtk_window_parse_geometry() called on a window with no visible children; the window should be set up before gtk_window_parse_geometry() is called. But if I remove the geometry setting from .Xdefaults, emacs seems to work fine. It's probably not worth pursuing these new problems until gvfs is ready, but I mentioned them in case they suggest to you that something is going on aside from the missing gvfs. The gtk3 build of emacs is available in the same place as before if you want to try it. Ken -- 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: Problems with emacs built against gtk3
On 12/4/2011 7:13 PM, Yaakov (Cygwin/X) wrote: On Fri, 2011-12-02 at 08:01 -0500, Ken Brown wrote: This doesn't do it. Emacs still dies after a short time. I don't know if that means that there's something else going on, but I'll retest it after you package gvfs. In the meantime, I'll continue with my workaround of setting GSETTINGS_BACKEND=memory. In case you (or anyone else) wants to experiment with this, you can get my build of the emacs-24 pretest by running setup.exe -K http://www.math.cornell.edu/~kbrown/kbrown.gpg and adding http://www.math.cornell.edu/~kbrown to the list of mirrors. WJFFM, but I'll get on that gvfs ITP right away. It looks like I also need to repackage pango1.0 to remove everyone's old pango.modules file. But despite your subject line, the binaries there are clearly gtk2 based. Was that intended? No, I made a mistake in my configure arguments. I put `--with-x=gtk3' instead of `--with-x-toolkit=gtk3', so emacs used the default gtk2. I'll rebuild it. Ken -- 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: Problems with emacs built against gtk3
On Sat, 2011-12-03 at 15:30 +0100, Angelo Graziosi wrote: > Just for completeness... > > Yaakov wrote > > > Okay, I got it. dconf-service needs a GVfs implementation, but the > > default provider (from the gvfs package) is currently only available in > > Ports. That's what I get for trying to be minimalistic wrt the distro. > > I installed gvfs and all it needs (I have many packages installed frp > cygports) but this doesn't fix the problem for me: Emacs still dies... :( I saw this as well, but with the 20111204 snapshot this no longer occurs. Could you try that and let us know? 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: Problems with emacs built against gtk3
On Fri, 2011-12-02 at 08:01 -0500, Ken Brown wrote: > This doesn't do it. Emacs still dies after a short time. I don't know > if that means that there's something else going on, but I'll retest it > after you package gvfs. In the meantime, I'll continue with my > workaround of setting GSETTINGS_BACKEND=memory. > > In case you (or anyone else) wants to experiment with this, you can get > my build of the emacs-24 pretest by running > > setup.exe -K http://www.math.cornell.edu/~kbrown/kbrown.gpg > > and adding http://www.math.cornell.edu/~kbrown to the list of mirrors. WJFFM, but I'll get on that gvfs ITP right away. It looks like I also need to repackage pango1.0 to remove everyone's old pango.modules file. But despite your subject line, the binaries there are clearly gtk2 based. Was that intended? 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: Problems with emacs built against gtk3
Hi, "Yaakov (Cygwin/X)" writes: > On Sat, 2011-11-26 at 08:40 -0500, Ken Brown wrote: >> On 11/25/2011 7:38 PM, Ken Brown wrote: >> > When I build emacs against gtk3, it is unusable. Here are the symptoms >> > when the resulting emacs is started in an xterm window: >> > >> > $ ./emacs -Q& >> > [1] 3344 >> > >> > (emacs:3344): GLib-WARNING **: In call to g_spawn_sync(), exit status of >> > a child process was requested but SIGCHLD action was set to SIG_IGN and >> > ECHILD was received by waitpid(), so exit status can't be returned. This >> > is a bug in the program calling g_spawn_sync(); either don't request the >> > exit status, or don't set the SIGCHLD action. >> > >> > ** (emacs:3344): WARNING **: Abnormal program termination spawning >> > command line `dbus-launch --autolaunch=0b8f184fe6d82872ee8db8724ecfdb90 >> > --binary-syntax --close-stderr': >> > >> > I think the pango warning is Cygwin specific, but the rest of it might >> > not be. Similar symptoms were reported on Fedora: >> > >> > https://bugzilla.redhat.com/show_bug.cgi?id=654027 > > This appears to be the same bug. The solution is to launch a DBus > session bus *before* starting emacs (or any other gtk3 programs for that > matter), IOW: > > $ eval `dbus-launch --sh-syntax` > $ emacs-X11 & > > The first command should be added to the beginning of your > ~/.startxwinrc, if you're using startxwin (or its shortcut) to start the > X server. I turned on DBUS debugging and it appears to be communicating before Emacs is started. Once emacs-X11 starts, it soon crashes: [...] GDBus-debug:Message: RECEIVED D-Bus message (72 bytes) Type:method-return Flags: no-reply-expected Version: 0 Serial: 3 Headers: reply-serial -> uint32 2 destination -> ':1.53' sender -> 'org.freedesktop.DBus' Body: () UNIX File Descriptors: (none) : 6c 02 01 01 00 00 00 00 03 00 00 00 35 00 00 00l...5... 0010: 06 01 73 00 05 00 00 00 3a 31 2e 35 33 00 00 00..s.:1.53... 0020: 05 01 75 00 02 00 00 00 07 01 73 00 14 00 00 00..u...s. 0030: 6f 72 67 2e 66 72 65 65 64 65 73 6b 74 6f 70 2eorg.freedesktop. 0040: 44 42 75 73 00 00 00 00 DBus GDBus-debug:Call: ASYNC COMPLETE org.freedesktop.DBus.AddMatch() (serial 2) SUCCESS Fatal error (11)Segmentation fault > > BTW, please be sure to reinstall dconf-service, that's not the problem, > and you're going to need it in the "new world order" of GNOME 3. > >> 2. The pango warning can already be observed with the current Cygwin >> emacs after the recent update of the GNOME libraries. To reproduce, >> install the emacs-X11 package and start emacs with the command `emacs &' >> in an xterm window. > > I cannot reproduce this. Does installing font-cantarell-otf help? > Perhaps another font? > > > 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: Problems with emacs built against gtk3
Just for completeness... Yaakov wrote Okay, I got it. dconf-service needs a GVfs implementation, but the default provider (from the gvfs package) is currently only available in Ports. That's what I get for trying to be minimalistic wrt the distro. I installed gvfs and all it needs (I have many packages installed frp cygports) but this doesn't fix the problem for me: Emacs still dies... :( Ciao, Angelo. -- 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: Problems with emacs built against gtk3
On 12/2/2011 5:35 AM, Yaakov (Cygwin/X) wrote: On Thu, 2011-12-01 at 18:04 -0500, Ken Brown wrote: On 11/30/2011 9:09 AM, Ken Brown wrote: On 11/29/2011 10:51 PM, Yaakov (Cygwin/X) wrote: This appears to be the same bug. The solution is to launch a DBus session bus *before* starting emacs (or any other gtk3 programs for that matter), IOW: $ eval `dbus-launch --sh-syntax` $ emacs-X11& That gets rid of the warning, but emacs still dies after a few seconds (no error message, no stackdump), unless I uninstall dconf-service. I'll see if I can get more information by running emacs under gdb. I'd appreciate any suggestions you might have as to where I should look. I have some further information: The problem is related to the GSettings backend. If I uninstall dconf-service and start emacs, I get a warning that the GSettings `memory' backend will be used. Emacs then works fine. If I reinstall dconf-service but set GSETTINGS_BACKEND=memory before starting emacs, it again works fine. Does this provide any clue as to what the problem might be? Okay, I got it. dconf-service needs a GVfs implementation, but the default provider (from the gvfs package) is currently only available in Ports. That's what I get for trying to be minimalistic wrt the distro. Of course, my gvfs package requires Avahi[1], so it may be an interesting ITP; I'll try to do that next week, and hopefully this thread will help expedite the review nonetheless. In the meantime, try setting the GIO_USE_VFS environment variable to "local"[2], which will allow dconf-service to work despite the lack of gvfs. (Why this isn't done automatically as a fallback, I have no idea.) This doesn't do it. Emacs still dies after a short time. I don't know if that means that there's something else going on, but I'll retest it after you package gvfs. In the meantime, I'll continue with my workaround of setting GSETTINGS_BACKEND=memory. In case you (or anyone else) wants to experiment with this, you can get my build of the emacs-24 pretest by running setup.exe -K http://www.math.cornell.edu/~kbrown/kbrown.gpg and adding http://www.math.cornell.edu/~kbrown to the list of mirrors. Ken -- 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: Problems with emacs built against gtk3
On Thu, 2011-12-01 at 18:04 -0500, Ken Brown wrote: > On 11/30/2011 9:09 AM, Ken Brown wrote: > > On 11/29/2011 10:51 PM, Yaakov (Cygwin/X) wrote: > >> This appears to be the same bug. The solution is to launch a DBus > >> session bus *before* starting emacs (or any other gtk3 programs for that > >> matter), IOW: > >> > >> $ eval `dbus-launch --sh-syntax` > >> $ emacs-X11& > > > > That gets rid of the warning, but emacs still dies after a few seconds > > (no error message, no stackdump), unless I uninstall dconf-service. I'll > > see if I can get more information by running emacs under gdb. I'd > > appreciate any suggestions you might have as to where I should look. > > > I have some further information: The problem is related to the GSettings > backend. If I uninstall dconf-service and start emacs, I get a warning > that the GSettings `memory' backend will be used. Emacs then works > fine. If I reinstall dconf-service but set GSETTINGS_BACKEND=memory > before starting emacs, it again works fine. Does this provide any clue > as to what the problem might be? Okay, I got it. dconf-service needs a GVfs implementation, but the default provider (from the gvfs package) is currently only available in Ports. That's what I get for trying to be minimalistic wrt the distro. Of course, my gvfs package requires Avahi[1], so it may be an interesting ITP; I'll try to do that next week, and hopefully this thread will help expedite the review nonetheless. In the meantime, try setting the GIO_USE_VFS environment variable to "local"[2], which will allow dconf-service to work despite the lack of gvfs. (Why this isn't done automatically as a fallback, I have no idea.) Yaakov Cygwin/X [1] http://cygwinports.blogspot.com/2011/07/this-lemur-can-be-found-outside-of.html [2] http://developer.gnome.org/gio/2.30/ch03.html -- 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: Problems with emacs built against gtk3
On 11/30/2011 9:09 AM, Ken Brown wrote: On 11/29/2011 10:51 PM, Yaakov (Cygwin/X) wrote: On Sat, 2011-11-26 at 08:40 -0500, Ken Brown wrote: On 11/25/2011 7:38 PM, Ken Brown wrote: When I build emacs against gtk3, it is unusable. Here are the symptoms when the resulting emacs is started in an xterm window: $ ./emacs -Q& [1] 3344 (emacs:3344): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. ** (emacs:3344): WARNING **: Abnormal program termination spawning command line `dbus-launch --autolaunch=0b8f184fe6d82872ee8db8724ecfdb90 --binary-syntax --close-stderr': I think the pango warning is Cygwin specific, but the rest of it might not be. Similar symptoms were reported on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=654027 This appears to be the same bug. The solution is to launch a DBus session bus *before* starting emacs (or any other gtk3 programs for that matter), IOW: $ eval `dbus-launch --sh-syntax` $ emacs-X11& That gets rid of the warning, but emacs still dies after a few seconds (no error message, no stackdump), unless I uninstall dconf-service. I'll see if I can get more information by running emacs under gdb. I'd appreciate any suggestions you might have as to where I should look. I forgot to say in my first post that the emacs I'm testing is a pretest of the upcoming emacs-24.1. If I'm not able to figure out what's going on, maybe I'll make an experimental version available so that you can try to reproduce the problem. I have some further information: The problem is related to the GSettings backend. If I uninstall dconf-service and start emacs, I get a warning that the GSettings `memory' backend will be used. Emacs then works fine. If I reinstall dconf-service but set GSETTINGS_BACKEND=memory before starting emacs, it again works fine. Does this provide any clue as to what the problem might be? Ken -- 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: Problems with emacs built against gtk3
On 11/29/2011 10:51 PM, Yaakov (Cygwin/X) wrote: On Sat, 2011-11-26 at 08:40 -0500, Ken Brown wrote: On 11/25/2011 7:38 PM, Ken Brown wrote: When I build emacs against gtk3, it is unusable. Here are the symptoms when the resulting emacs is started in an xterm window: $ ./emacs -Q& [1] 3344 (emacs:3344): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. ** (emacs:3344): WARNING **: Abnormal program termination spawning command line `dbus-launch --autolaunch=0b8f184fe6d82872ee8db8724ecfdb90 --binary-syntax --close-stderr': I think the pango warning is Cygwin specific, but the rest of it might not be. Similar symptoms were reported on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=654027 This appears to be the same bug. The solution is to launch a DBus session bus *before* starting emacs (or any other gtk3 programs for that matter), IOW: $ eval `dbus-launch --sh-syntax` $ emacs-X11& That gets rid of the warning, but emacs still dies after a few seconds (no error message, no stackdump), unless I uninstall dconf-service. I'll see if I can get more information by running emacs under gdb. I'd appreciate any suggestions you might have as to where I should look. I forgot to say in my first post that the emacs I'm testing is a pretest of the upcoming emacs-24.1. If I'm not able to figure out what's going on, maybe I'll make an experimental version available so that you can try to reproduce the problem. Ken -- 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: Problems with emacs built against gtk3
On 11/30/2011 6:54 AM, Yaakov (Cygwin/X) wrote: On Wed, 2011-11-30 at 11:17 +0100, Pavel Holejsovsky wrote: On 11/30/2011 4:51 AM, Yaakov (Cygwin/X) wrote: 2. The pango warning can already be observed with the current Cygwin emacs after the recent update of the GNOME libraries. To reproduce, install the emacs-X11 package and start emacs with the command `emacs&' in an xterm window. I cannot reproduce this. Does installing font-cantarell-otf help? Perhaps another font? I can reproduce it, in fact almost every gtk-enabled application spits that out. I tried stracing, and I think (but I'm not sure) that the warning appears after pango tries to load /usr/lib/pango/1.6.0/modules/pango-basic-fc.dll -> there is no /usr/lib/pango directory on my system, and it seems that no package in cygwin or ports repository provides it. That's the clue I needed. I switched pango to builtin modules over a year ago in Ports to help minimize fork() errors, but that didn't reach the distro until now. If I'm right, removing /etc/pango/pango.modules should fix it. That fixes it. Thanks. Ken -- 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: Problems with emacs built against gtk3
On Wed, 2011-11-30 at 11:17 +0100, Pavel Holejsovsky wrote: > On 11/30/2011 4:51 AM, Yaakov (Cygwin/X) wrote: > >> 2. The pango warning can already be observed with the current Cygwin > >> emacs after the recent update of the GNOME libraries. To reproduce, > >> install the emacs-X11 package and start emacs with the command `emacs&' > >> in an xterm window. > > > > I cannot reproduce this. Does installing font-cantarell-otf help? > > Perhaps another font? > > I can reproduce it, in fact almost every gtk-enabled application spits > that out. I tried stracing, and I think (but I'm not sure) that the > warning appears after pango tries to load > /usr/lib/pango/1.6.0/modules/pango-basic-fc.dll -> there is no > /usr/lib/pango directory on my system, and it seems that no package in > cygwin or ports repository provides it. That's the clue I needed. I switched pango to builtin modules over a year ago in Ports to help minimize fork() errors, but that didn't reach the distro until now. If I'm right, removing /etc/pango/pango.modules should fix it. 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: Problems with emacs built against gtk3
On 11/30/2011 4:51 AM, Yaakov (Cygwin/X) wrote: 2. The pango warning can already be observed with the current Cygwin emacs after the recent update of the GNOME libraries. To reproduce, install the emacs-X11 package and start emacs with the command `emacs&' in an xterm window. I cannot reproduce this. Does installing font-cantarell-otf help? Perhaps another font? I can reproduce it, in fact almost every gtk-enabled application spits that out. I tried stracing, and I think (but I'm not sure) that the warning appears after pango tries to load /usr/lib/pango/1.6.0/modules/pango-basic-fc.dll -> there is no /usr/lib/pango directory on my system, and it seems that no package in cygwin or ports repository provides it. HTH, Pavel -- 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: Problems with emacs built against gtk3
On Sat, 2011-11-26 at 08:40 -0500, Ken Brown wrote: > On 11/25/2011 7:38 PM, Ken Brown wrote: > > When I build emacs against gtk3, it is unusable. Here are the symptoms > > when the resulting emacs is started in an xterm window: > > > > $ ./emacs -Q& > > [1] 3344 > > > > (emacs:3344): GLib-WARNING **: In call to g_spawn_sync(), exit status of > > a child process was requested but SIGCHLD action was set to SIG_IGN and > > ECHILD was received by waitpid(), so exit status can't be returned. This > > is a bug in the program calling g_spawn_sync(); either don't request the > > exit status, or don't set the SIGCHLD action. > > > > ** (emacs:3344): WARNING **: Abnormal program termination spawning > > command line `dbus-launch --autolaunch=0b8f184fe6d82872ee8db8724ecfdb90 > > --binary-syntax --close-stderr': > > > > I think the pango warning is Cygwin specific, but the rest of it might > > not be. Similar symptoms were reported on Fedora: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=654027 This appears to be the same bug. The solution is to launch a DBus session bus *before* starting emacs (or any other gtk3 programs for that matter), IOW: $ eval `dbus-launch --sh-syntax` $ emacs-X11 & The first command should be added to the beginning of your ~/.startxwinrc, if you're using startxwin (or its shortcut) to start the X server. BTW, please be sure to reinstall dconf-service, that's not the problem, and you're going to need it in the "new world order" of GNOME 3. > 2. The pango warning can already be observed with the current Cygwin > emacs after the recent update of the GNOME libraries. To reproduce, > install the emacs-X11 package and start emacs with the command `emacs &' > in an xterm window. I cannot reproduce this. Does installing font-cantarell-otf help? Perhaps another font? 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: Problems with emacs built against gtk3
Ken Brown wrote: I don't think gtk3 is the culprit here after all. I uninstalled libgtk3_0 and libgtk3-devel and rebuilt emacs, but the problem persisted. It was only after uninstalling dconf-service (a dependency of libgtk3_0) that things went back to normal. I can confirm. I uninstalled (forcing) ONLY dconf-service and Emacs works again. Thanks to Ken for having found this workaround... Ciao, Angelo. -- 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: Problems with emacs built against gtk3
On 11/25/2011 7:38 PM, Ken Brown wrote: When I build emacs against gtk3, it is unusable. Here are the symptoms when the resulting emacs is started in an xterm window: $ ./emacs -Q& [1] 3344 (emacs:3344): GLib-WARNING **: In call to g_spawn_sync(), exit status of a child process was requested but SIGCHLD action was set to SIG_IGN and ECHILD was received by waitpid(), so exit status can't be returned. This is a bug in the program calling g_spawn_sync(); either don't request the exit status, or don't set the SIGCHLD action. ** (emacs:3344): WARNING **: Abnormal program termination spawning command line `dbus-launch --autolaunch=0b8f184fe6d82872ee8db8724ecfdb90 --binary-syntax --close-stderr': (emacs:3344): Pango-WARNING **: No such file or directory A few seconds later, emacs dies (the window disappears and the process is gone, with no error messages), and two dbus processes remain: $ ps | grep dbus 5188 1 3344 5188 7 1002 19:07:31 /usr/bin/dbus-launch 6452 1 6452 6452 ? 1002 19:07:31 /usr/bin/dbus-daemon If I start emacs again without killing the dbus processes, I don't get the first two warnings but I still get the third. Again, emacs dies after a few seconds. I think the pango warning is Cygwin specific, but the rest of it might not be. Similar symptoms were reported on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=654027 But there are some differences, so I thought I should report it here just in case part of the problem is Cygwin specific. My cygcheck output is attached but probably not relevant. Further info: 1. I don't think gtk3 is the culprit here after all. I uninstalled libgtk3_0 and libgtk3-devel and rebuilt emacs, but the problem persisted. It was only after uninstalling dconf-service (a dependency of libgtk3_0) that things went back to normal [except for the pango warning]. 2. The pango warning can already be observed with the current Cygwin emacs after the recent update of the GNOME libraries. To reproduce, install the emacs-X11 package and start emacs with the command `emacs &' in an xterm window. Ken -- 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/
