all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sebas Olsson <visnae@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 30551@debbugs.gnu.org
Subject: bug#30551: 25.3; Core dump on GTK with -Q
Date: Mon, 5 Mar 2018 09:31:12 +0100	[thread overview]
Message-ID: <CAH+QApBMeyq7b8JLMXdPJyv6btLYUaW+qhKQfdoQLBcVkis2Ow@mail.gmail.com> (raw)
In-Reply-To: <87woyu2isc.fsf@gmail.com>

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

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@gmail.com> wrote:

> tags 30551 + moreinfo
> quit
>
> Sebas Olsson <visnae@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
>

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

  reply	other threads:[~2018-03-05  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20  8:03 bug#30551: 25.3; Core dump on GTK with -Q Sebas Olsson
2018-03-02 22:51 ` Noam Postavsky
2018-03-05  8:31   ` Sebas Olsson [this message]
2018-03-05 23:29     ` Noam Postavsky

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

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

  git send-email \
    --in-reply-to=CAH+QApBMeyq7b8JLMXdPJyv6btLYUaW+qhKQfdoQLBcVkis2Ow@mail.gmail.com \
    --to=visnae@gmail.com \
    --cc=30551@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.