GNU bug report logs - #30551
25.3; Core dump on GTK with -Q

Previous Next

Package: emacs;

Reported by: Sebas Olsson <visnae <at> gmail.com>

Date: Tue, 20 Feb 2018 16:37:02 UTC

Severity: normal

Tags: notabug

Merged with 30558, 30653

Found in versions 25.3, 26.0.90

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=105135

Full log


Message #13 received at 30551 <at> debbugs.gnu.org (full text, mbox):

From: Sebas Olsson <visnae <at> gmail.com>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 30551 <at> debbugs.gnu.org
Subject: Re: bug#30551: 25.3; Core dump on GTK with -Q
Date: Mon, 5 Mar 2018 09:31:12 +0100
[Message part 1 (text/plain, inline)]
Yes, you are probably right, I upgraded mesa today (17.3.5-1 -> 17.3.6-1)
and I can no longer reproduce this.

Do you still want me to build emacs with debug, and downgrade mesa to prove
it?

I'm happy with this result so we could close this bug.


On 2 March 2018 at 23:51, Noam Postavsky <npostavs <at> gmail.com> wrote:

> tags 30551 + moreinfo
> quit
>
> Sebas Olsson <visnae <at> gmail.com> writes:
>
> > This started yesterday as I updated both Emacs, Kernel, X as well as
> > some other packages with `pacman -Syu`.
> >
> > I have some other crashes from other programs in journalctl. The
> > system
> > seems to be stable when not running emacs (or only `emacs -nw`).
> >
> > Please let me know if you need journal or pacman logs.
> >
> > Stack trace for emacs from journalctl:
>
> Can you build Emacs with debug symbols, so we can get a more informative
> backtrace?  Is it possible this is the same as Bug#30653 (which turned
> out to be a mesa bug)?
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30653
>
[Message part 2 (text/html, inline)]

This bug report was last modified 7 years and 65 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.