From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98520] System randomly crashes / freezes while playing certain games
Date: Wed, 04 Apr 2018 00:45:54 +0000 [thread overview]
Message-ID: <bug-98520-502-8IKiPrLpQx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98520-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1036 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98520
Timothy Arceri <t_arceri@yahoo.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |FIXED
--- Comment #42 from Timothy Arceri <t_arceri@yahoo.com.au> ---
(In reply to MirceaKitsune from comment #41)
> (In reply to wbrana from comment #40)
>
> Hi. I do not run Ubuntu, just openSUSE Tumbleweed. However they finally
> upgraded to Mesa 17.3.2 recently, so I may test more games soon and see if
> there are any crashes left. Since I reported this nearly two years ago, the
> original crash was most certainly lost in all the changes done since... new
> ones may still exist however.
In that case we should close this bug. Please open a fresh bug report for any
new issues. Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2711 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-04 0:45 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 20:18 [Bug 98520] System randomly crashes / freezes while playing certain games bugzilla-daemon
2016-10-31 20:21 ` bugzilla-daemon
2016-10-31 20:23 ` bugzilla-daemon
2016-10-31 20:26 ` bugzilla-daemon
2016-10-31 20:29 ` bugzilla-daemon
2016-10-31 20:32 ` bugzilla-daemon
2016-10-31 20:40 ` bugzilla-daemon
2016-10-31 20:43 ` bugzilla-daemon
2016-10-31 22:43 ` bugzilla-daemon
2016-11-01 1:04 ` bugzilla-daemon
2016-11-01 1:21 ` bugzilla-daemon
2016-11-01 18:46 ` bugzilla-daemon
2016-11-21 3:52 ` bugzilla-daemon
2016-11-21 3:54 ` bugzilla-daemon
2016-12-02 0:53 ` bugzilla-daemon
2016-12-21 7:32 ` bugzilla-daemon
2016-12-24 0:57 ` bugzilla-daemon
2016-12-27 4:14 ` bugzilla-daemon
2016-12-27 14:17 ` bugzilla-daemon
2016-12-28 2:56 ` bugzilla-daemon
2016-12-28 20:27 ` bugzilla-daemon
2017-01-01 14:42 ` bugzilla-daemon
2017-01-01 18:21 ` bugzilla-daemon
2017-01-01 18:27 ` bugzilla-daemon
2017-01-05 1:51 ` bugzilla-daemon
2017-01-05 11:14 ` bugzilla-daemon
2017-01-05 12:33 ` bugzilla-daemon
2017-01-06 8:36 ` bugzilla-daemon
2017-01-06 8:52 ` bugzilla-daemon
2017-01-13 15:22 ` bugzilla-daemon
2017-01-18 14:07 ` bugzilla-daemon
2017-01-19 6:20 ` bugzilla-daemon
2017-01-20 14:26 ` bugzilla-daemon
2017-01-21 7:17 ` bugzilla-daemon
2017-01-21 17:51 ` bugzilla-daemon
2017-01-23 10:38 ` bugzilla-daemon
2017-01-24 6:27 ` bugzilla-daemon
2017-03-03 0:50 ` bugzilla-daemon
2017-03-03 1:14 ` bugzilla-daemon
2017-04-02 15:33 ` bugzilla-daemon
2017-05-01 23:19 ` bugzilla-daemon
2017-09-19 8:11 ` bugzilla-daemon
2018-01-19 13:24 ` bugzilla-daemon
2018-01-19 14:28 ` bugzilla-daemon
2018-04-04 0:45 ` bugzilla-daemon [this message]
2018-04-04 1:05 ` bugzilla-daemon
2018-04-04 1:06 ` bugzilla-daemon
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=bug-98520-502-8IKiPrLpQx@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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.
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.