public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin-xfree@cygwin.com
Subject: Emacs problems after dbus (?) update
Date: Sat, 03 Dec 2011 06:45:00 -0000	[thread overview]
Message-ID: <CAK-n8j7TedOTJBdJugQDtCv4=ojq2iFsUR5rpqRYAtkyqEPhxA@mail.gmail.com> (raw)

I updated Cygwin today, I think there was a dbus update.  Now
emacs-x11 is complaining:


lrwxrwxrwx 1 Jim Reisert None 23 Aug 17 23:03 /usr/bin/emacs ->
/etc/alternatives/emacs
lrwxrwxrwx 1 Jim Reisert None 22 Aug 17 23:03 /etc/alternatives/emacs
-> /usr/bin/emacs-X11.exe


JJR:~> emacs

(emacs:3380): GLib-GObject-WARNING **: Two different plugins tried to
register 'BasicEngineFc'.

(emacs:3380): GLib-GObject-CRITICAL **: g_object_new: assertion
`G_TYPE_IS_OBJECT (object_type)' failed

(emacs:3380): Pango-WARNING **: Failed to load Pango module
'/usr/lib/pango/1.6.0/modules/pango-basic-fc.dll' for id
'BasicScriptEngineFc'

(emacs:3380): GLib-GObject-WARNING **: Two different plugins tried to
register 'BasicEngineFc'.

(emacs:3380): GLib-GObject-CRITICAL **: g_object_new: assertion
`G_TYPE_IS_OBJECT (object_type)' failed



(the last pair is repeated over and over again).

Should I rebase, or did something go horribly wrong?

- Jim

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

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


             reply	other threads:[~2011-12-03  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03  6:45 Jim Reisert AD1C [this message]
2011-12-03 14:24 ` Ken Brown
2011-12-03 16:25   ` Jim Reisert AD1C
2011-12-03 18:30     ` Ken Brown

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='CAK-n8j7TedOTJBdJugQDtCv4=ojq2iFsUR5rpqRYAtkyqEPhxA@mail.gmail.com' \
    --to=jjreisert@alum.mit.edu \
    --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).