[Bug 1710897] Re: emacs25-x crashed with SIGABRT in raise()

2017-10-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: emacs25 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to emacs25 in Ubuntu.
https://bugs.launchpad.net/bugs/1710897

Title:
  emacs25-x crashed with SIGABRT in raise()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1710897/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1710897] Re: emacs25-x crashed with SIGABRT in raise()

2017-08-27 Thread Glenn Morris
"Connection lost to X server", so this sounds like the following entry
from Emacs's etc/PROBLEMS:

** When Emacs is compiled with Gtk+, closing a display kills Emacs.

There is a long-standing bug in GTK that prevents it from recovering
from disconnects: http://bugzilla.gnome.org/show_bug.cgi?id=85715.

Thus, for instance, when Emacs is run as a server on a text terminal,
and an X frame is created, and the X server for that frame crashes or
exits unexpectedly, Emacs must exit to prevent a GTK error that would
result in an endless loop.

If you need Emacs to be able to recover from closing displays, compile
it with the Lucid toolkit instead of GTK.


** Bug watch added: GNOME Bug Tracker #85715
   https://bugzilla.gnome.org/show_bug.cgi?id=85715

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to emacs25 in Ubuntu.
https://bugs.launchpad.net/bugs/1710897

Title:
  emacs25-x crashed with SIGABRT in raise()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1710897/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs