From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 62870] New: Steam.sh fails at line 704, possibly relating to mesa stack
Date: Thu, 28 Mar 2013 15:52:44 +0000 [thread overview]
Message-ID: <bug-62870-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=62870
Priority: medium
Bug ID: 62870
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: Steam.sh fails at line 704, possibly relating to mesa
stack
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: xpaulramundox-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/DRI/nouveau
Product: Mesa
Created attachment 77163
--> https://bugs.freedesktop.org/attachment.cgi?id=77163&action=edit
debug info from steam.sh
After trying to load steam, I have come across an error at line 704 that
prevents steam from properly starting. Attached is the debug information from
the crash:
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2335 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2013-03-28 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 15:52 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-62870-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-06-20 1:07 ` [Bug 62870] Steam.sh fails at line 704, possibly relating to mesa stack bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 6:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-62870-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.