public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: nyc4bos@aol.com
To: cygwin-xfree@cygwin.com
Subject: Re: Problems with emacs built against gtk3
Date: Mon, 05 Dec 2011 00:13:00 -0000	[thread overview]
Message-ID: <83zkf94bt3.fsf@aol.com> (raw)
In-Reply-To: <1322625099.6420.9.camel@YAAKOV04>

Hi,

"Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net> 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)
  0000: 6c 02 01 01  00 00 00 00  03 00 00 00  35 00 00 00    l...........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 2e    org.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/


  parent reply	other threads:[~2011-12-03 20:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26  0:39 Ken Brown
2011-11-26 13:40 ` Ken Brown
2011-11-30  3:52   ` Yaakov (Cygwin/X)
2011-11-30 10:25     ` Pavel Holejsovsky
2011-11-30 11:54       ` Yaakov (Cygwin/X)
2011-11-30 12:27         ` Ken Brown
2011-12-10 12:14           ` nyc4bos
2011-12-13 18:51             ` Ken Brown
2011-11-30 14:09     ` Ken Brown
2011-12-02 10:36       ` Ken Brown
2011-12-02 13:01         ` Yaakov (Cygwin/X)
2011-12-03  2:30           ` Ken Brown
2011-12-05  0:22             ` Yaakov (Cygwin/X)
2011-12-05 13:28               ` Ken Brown
2011-12-10  1:40                 ` Ken Brown
2012-04-03 21:13               ` Ken Brown
2012-04-03 22:30                 ` Yaakov (Cygwin/X)
2012-04-04  1:53                   ` Ken Brown
2012-04-04  3:56                     ` Yaakov (Cygwin/X)
2012-04-04 14:15                       ` Ken Brown
2012-04-04 22:13                         ` Yaakov (Cygwin/X)
2012-04-06 17:22                           ` Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3] Ken Brown
2011-12-05  0:13     ` nyc4bos [this message]
2011-11-28  8:49 Problems with emacs built against gtk3 Angelo Graziosi
2011-12-03 15:18 ` Angelo Graziosi
2011-12-05  0:38   ` Yaakov (Cygwin/X)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zkf94bt3.fsf@aol.com \
    --to=nyc4bos@aol.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).