I've restarted my X session, and connect to the still running emacs
daemon via emacsclient no longer works. X window is created, but
nothing is ever drawn inside it.
Fortunately, emacsclient -t works, so I don't lose information.
However, I wish to try to debug the problem. What should I do?
Andrey Paramonov
FYI, this seems quite common. If X falls over here with an X
emacsclient open I get the same issue (Debian with Gnome). Interestingly
enough I hadn't thought to connect using emacsclient -t so thanks for
that!
I do not have a clear picture of what it is you are doing, but I can
see two possible reasons: a security cooky is renewed, and a file in
/tmp is stalled.
Is not there a way to restart the daemon?
Ilya
Is your Emacs compiled to use the GTK toolkit? There are long
standing bugs regarding the inability of GTK to handle the initial X
display being closed.
Yes, it is.
So, is anyone interested in debug information I can gather? If so,
please tell me what should I do. Otherwise I'll just restart the
daemon.
Andrey
> Hello!
>
> I've restarted my X session, and connect to the still running emacs
> daemon via emacsclient no longer works. X window is created, but
> nothing is ever drawn inside it.
>
> Fortunately, emacsclient -t works, so I don't lose information.
> However, I wish to try to debug the problem. What should I do?
Does your emacs use the Gtk+ toolkit?
If yes, then this is a (very) long standing problem in Gtk+:
http://bugzilla.gnome.org/show_bug.cgi?id=85715
there are some workarounds for this in emacs, but it cannot be fixed
until Gtk+ is fixed (not very likely, it seems).
This problem gets reported from time to time...
If emacs is configured using --with-x-toolkit=lucid you will not have
this problem.