unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: ricercar@lycos.com
To: Eli Zaretskii <eliz@gnu.org>
Cc: 38837@debbugs.gnu.org
Subject: bug#38837: 26.3.50; Segmentation Fault with Desktop Save Mode (emacs 26.3.50)
Date: Fri, 3 Jan 2020 06:12:58 +0000	[thread overview]
Message-ID: <1450fc3c-d52f-a0c9-e16c-b50554b0403f@lycos.com> (raw)
In-Reply-To: <831rsjlu9g.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

It seems to be fixed in 27. Any idea how I can avoid the problem in a stable
release, such as 26 or 25?

On 1/1/20 3:39 AM, Eli Zaretskii wrote:

>> From: ricercar@lycos.com
>> Date: Tue, 31 Dec 2019 20:03:24 +0000
>>
>> When I try to run emacs 26.3.50 (built from source), it gives me the following warning: "Warning: desktop file appears to be in use by PID .... Using it may cause conflicts. Use it anyway? (y or n)". If I select "y", it eventually quits and the following error is produced:
>>
>> Fatal error 11: Segmentation fault
>> Backtrace:
>> ./src/emacs-26.3.50.1[0x5072fe]
>> ./src/emacs-26.3.50.1[0x4ece6a]
>> ./src/emacs-26.3.50.1[0x50581e]
>> ./src/emacs-26.3.50.1[0x505a38]
>> ./src/emacs-26.3.50.1[0x505abc]
>> /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f0e498eb890]
>> /usr/lib/x86_64-linux-gnu/libXft.so.2(XftCharIndex+0xd)[0x7f0e4a9bb68d]
> Crystal ball says this is bug#38442.  If so, it is already fixed, and
> the problem is that you have a non-XFT font backend specified by the
> desktop file for one of your frames.
>

[-- Attachment #2: Type: text/html, Size: 1529 bytes --]

  reply	other threads:[~2020-01-03  6:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31 20:03 bug#38837: 26.3.50; Segmentation Fault with Desktop Save Mode (emacs 26.3.50) ricercar
2020-01-01  3:39 ` Eli Zaretskii
2020-01-03  6:12   ` ricercar [this message]
2020-01-03  7:56     ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=1450fc3c-d52f-a0c9-e16c-b50554b0403f@lycos.com \
    --to=ricercar@lycos.com \
    --cc=38837@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).