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:
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
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...
Cia
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 thi
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 com
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
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 reall
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 gv
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 i
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. (
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
em
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
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 packag
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 continu
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 b
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 GSETTIN
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&
>> > [
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 m
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
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
> >
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
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
(e
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,
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 s
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 reprodu
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
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 (f
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 bu
28 matches
Mail list logo