GNU bug report logs -
#1708
23.0.60; g_main_context_prepare() called recursively
Previous Next
Reported by: Markus Triska <markus.triska <at> gmx.at>
Date: Fri, 26 Dec 2008 12:10:03 UTC
Severity: normal
Tags: moreinfo, unreproducible
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 1708 in the body.
You can then email your comments to 1708 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1708
; Package
emacs
.
(Fri, 26 Dec 2008 12:10:04 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Markus Triska <markus.triska <at> gmx.at>
:
New bug report received and forwarded. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
(Fri, 26 Dec 2008 12:10:04 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):
From OSX 10.4, I log in via ssh to a remote machine R running Ubuntu
jaunty, and there do:
$ emacs -nw -Q -f server-start
In another terminal in OSX, I again ssh to R, and there do:
$ emacsclient -c
As expected, I get an X frame on the local machine (OSX). Now I close
the terminal in which I started the remote emacsclient, thus killing
the client. The remote server at this point shows the message:
server: Connection lost to X server `localhost:11.0'
Now I again ssh to R, and again do there:
$ emacsclient -c
Now, only a blank frame shows up, and the remote server repeatedly
shows the following message:
(emacs:11624): GLib-WARNING **: g_main_context_prepare() called
recursively from within a source's check() or prepare() member.
Information about Emacs on the remote machine R:
In GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.14.5)
of 2008-12-24 on R
Windowing system distributor `The XFree86 Project, Inc', version 11.0.40400000
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_US.UTF-8
value of $XMODIFIERS: nil
locale-coding-system: utf-8-unix
default-enable-multibyte-characters: t
This also works when I ssh from R to R itself, i.e., I can reproduce
the problem in Ubuntu jaunty alone as well.
In GNU Emacs 23.0.60.1 (i386-apple-darwin8.11.1, GTK+ Version 2.12.9)
of 2008-12-25 on mt-computer.local
Windowing system distributor `The XFree86 Project, Inc', version 11.0.40400000
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_GB.UTF-8
value of $XMODIFIERS: nil
locale-coding-system: nil
default-enable-multibyte-characters: t
Information forwarded
to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1708
; Package
emacs
.
(Sat, 27 Dec 2008 17:25:04 GMT)
Full text and
rfc822 format available.
Message #8 received at 1708 <at> emacsbugs.donarmstrong.com (full text, mbox):
Markus Triska <markus.triska <at> gmx.at> writes:
> From OSX 10.4, I log in via ssh to a remote machine R running Ubuntu
> jaunty, and there do:
>
> $ emacs -nw -Q -f server-start
>
> In another terminal in OSX, I again ssh to R, and there do:
>
> $ emacsclient -c
>
> As expected, I get an X frame on the local machine (OSX). Now I close
> the terminal in which I started the remote emacsclient, thus killing
> the client. The remote server at this point shows the message:
>
> server: Connection lost to X server `localhost:11.0'
>
> Now I again ssh to R, and again do there:
>
> $ emacsclient -c
>
> Now, only a blank frame shows up, and the remote server repeatedly
> shows the following message:
>
> (emacs:11624): GLib-WARNING **: g_main_context_prepare() called
> recursively from within a source's check() or prepare() member.
>
> Information about Emacs on the remote machine R:
>
> In GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.14.5)
> of 2008-12-24 on R
Can you reproduce this when configuring without GTK+?
If not, this and your other disconnect bug are probably just instances
of the same very old Gtk+ bug: http://bugzilla.gnome.org/show_bug.cgi?id=85715.
Gtk+ does deal well with disconnecting...
Information forwarded
to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1708
; Package
emacs
.
(Wed, 31 Dec 2008 16:35:03 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Markus Triska <markus.triska <at> gmx.at>
:
Extra info received and forwarded to list. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
(Wed, 31 Dec 2008 16:35:03 GMT)
Full text and
rfc822 format available.
Message #13 received at 1708 <at> emacsbugs.donarmstrong.com (full text, mbox):
Dan Nicolaescu <dann <at> ics.uci.edu> writes:
> Can you reproduce this when configuring without GTK+?
With --with-x-toolkit=lucid, the second "emacsclient -c" shows:
Waiting for Emacs...
*ERROR*: X protocol error: BadLength (poly request too large or internal
Xlib length error) on protocol request 19
After a few further $ emacsclient -c, the server always crashes with:
#0 0x0003392d in redisplay_internal (preserve_echo_area=0) at
xdisp.c:11800#1 0x000342f6 in redisplay_preserve_echo_area
(from_where=12) at xdisp.c:12040#2 0x001920a7 in
wait_reading_process_output (time_limit=30, microsecs=0, read_kbd=-1,
do_display=1, wait_for_cell=50332681, wait_proc=0x0, just_wait_proc=0)
at process.c:4997#3 0x0000c01e in sit_for (timeout=240, reading=1,
do_display=1) at dispnew.c:6637#4 0x000e8c9a in read_char
(commandflag=1, nmaps=2, maps=0xbffff3d0, prev_event=50332681,
used_mouse_menu=0xbffff4c8, end_time=0x0) at keyboard.c:2903#5
0x000eaa0a in read_key_sequence (keybuf=0xbffff588, bufsize=30,
prompt=50332681, dont_downcase_last=0, can_return_switch_frame=1,
fix_current_buffer=1) at keyboard.c:9354#6 0x000ece2b in command_loop_1
() at keyboard.c:1632#7 0x0014c94c in internal_condition_case
(bfun=0xecc0d <command_loop_1>, handlers=50372345, hfun=0xe59a8
<cmd_error>) at eval.c:1511#8 0x000ded84 in command_loop_2 () at
keyboard.c:1349#9 0x0014c59e in internal_catch (tag=50368417,
func=0xded40 <command_loop_2>, arg=50332681) at eval.c:1247#10
0x000deb26 in command_loop () at keyboard.c:1328#11 0x000debdf in
recursive_edit_1 () at keyboard.c:942#12 0x000ded27 in Frecursive_edit
() at keyboard.c:1004#13 0x000ddb3c in main (argc=5, argv=0xbffff9c0)
at emacs.c:1786
Information forwarded
to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1708
; Package
emacs
.
(Wed, 31 Dec 2008 16:45:03 GMT)
Full text and
rfc822 format available.
Message #16 received at 1708 <at> emacsbugs.donarmstrong.com (full text, mbox):
Markus Triska <markus.triska <at> gmx.at> writes:
> Dan Nicolaescu <dann <at> ics.uci.edu> writes:
>
> > Can you reproduce this when configuring without GTK+?
>
> With --with-x-toolkit=lucid, the second "emacsclient -c" shows:
>
> Waiting for Emacs...
> *ERROR*: X protocol error: BadLength (poly request too large or internal
> Xlib length error) on protocol request 19
>
> After a few further $ emacsclient -c, the server always crashes with:
I can't reproduce this on an Fedora 10 machine...
Added tag(s) unreproducible and moreinfo.
Request was from
Chong Yidong <cyd <at> stupidchicken.com>
to
control <at> debbugs.gnu.org
.
(Thu, 24 Jun 2010 18:24:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#1708
; Package
emacs
.
(Thu, 06 Feb 2014 01:09:01 GMT)
Full text and
rfc822 format available.
Message #21 received at 1708 <at> debbugs.gnu.org (full text, mbox):
Markus Triska <markus.triska <at> gmx.at> writes:
>> Can you reproduce this when configuring without GTK+?
>
> With --with-x-toolkit=lucid, the second "emacsclient -c" shows:
>
> Waiting for Emacs...
> *ERROR*: X protocol error: BadLength (poly request too large or internal
> Xlib length error) on protocol request 19
>
> After a few further $ emacsclient -c, the server always crashes with:
>
> #0 0x0003392d in redisplay_internal (preserve_echo_area=0) at
> xdisp.c:11800#1 0x000342f6 in redisplay_preserve_echo_area
Are you still seeing this in Emacs 24.3?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#1708
; Package
emacs
.
(Thu, 06 Feb 2014 18:34:02 GMT)
Full text and
rfc822 format available.
Message #24 received at 1708 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> Are you still seeing this in Emacs 24.3?
No, since I am no longer using emacsclient due to its memory leaks (#1504).
bug closed, send any further explanations to
1708 <at> debbugs.gnu.org and Markus Triska <markus.triska <at> gmx.at>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 07 Feb 2014 00:12:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 07 Mar 2014 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 11 years and 186 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.