Since this no longer seems to be a Fedora specific issue, I have filed a
bug upstream with Mesa. Thanks to everyone for your help.
https://bugs.freedesktop.org/show_bug.cgi?id=67690
Morgan
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
After upgrading from F18 to F19 using fedup, I was getting a segfault
starting Xorg[1]. It turns out my case seemed almost identical to another
case[2], but since they seemed to be from separate drivers I filed a
separate bug. The catalyst driver also did not work for me, but for an
entirely
On Thu, 2013-08-01 at 20:21 +0800, Morgan Howe wrote:
After upgrading from F18 to F19 using fedup, I was getting a segfault
starting Xorg[1]. It turns out my case seemed almost identical to
another case[2], but since they seemed to be from separate drivers I
filed a separate bug. The catalyst
On Thu, Aug 1, 2013 at 11:12 PM, Adam Williamson awill...@redhat.comwrote:
On Thu, 2013-08-01 at 20:21 +0800, Morgan Howe wrote:
The latest mesa in the repos still does not solve this problem, so I
just wanted to bring it to the maintainer's attention that an update
for this package should
On Thu, Aug 1, 2013 at 3:50 PM, Morgan Howe mth...@gmail.com wrote:
I didn't say you need to bump it to bleeding edge git. I'm just letting you
know that there's a pretty serious bug in the current version of mesa that
is affecting at least a few people - probably even more who just rolled back
- Original Message -
From: Jef Spaleta jspal...@gmail.com
To: Development discussions related to Fedora
devel@lists.fedoraproject.org
Sent: Friday, 2 August, 2013 10:14:31 AM
Subject: Re: Mesa needs an update?
On Thu, Aug 1, 2013 at 3:50 PM, Morgan Howe mth...@gmail.com wrote
On Fri, Aug 2, 2013 at 8:14 AM, Jef Spaleta jspal...@gmail.com wrote:
On Thu, Aug 1, 2013 at 3:50 PM, Morgan Howe mth...@gmail.com wrote:
I didn't say you need to bump it to bleeding edge git. I'm just letting
you
know that there's a pretty serious bug in the current version of mesa
that
On Fri, Aug 2, 2013 at 8:38 AM, David Airlie airl...@redhat.com wrote:
Also unless he rebuild the upstream mesa in rpm with the same flags, I'm
not sure
this is guaranteed fixed upstream.
I'd be happy to help debug this. I'm currently trying to find where I can
see the flags used for the
On Thu, Aug 1, 2013 at 4:38 PM, Morgan Howe mth...@gmail.com wrote:
That may have been a mistake on my part due to lack of knowledge on your
bugzilla workflow, apologies for that. I haven't filed a bug report before
and wasn't sure how that should be handled. I've reassigned the bug from
On Fri, Aug 2, 2013 at 8:57 AM, Jef Spaleta jspal...@gmail.com wrote:
My rule of thumb... I only close the bugs I open under two conditions:
I've figured out it was user error or misconfiguration on my part (hey
it happens to all of us) or I can confirm the fix has propagated into
the
On Fri, Aug 2, 2013 at 8:38 AM, David Airlie airl...@redhat.com wrote:
Also unless he rebuild the upstream mesa in rpm with the same flags, I'm
not sure
this is guaranteed fixed upstream.
Dave, for the sake of having the conversation in a single place, I'm
responding to your comment on
On Fri, Aug 2, 2013 at 9:22 AM, Morgan Howe mth...@gmail.com wrote:
On Fri, Aug 2, 2013 at 8:38 AM, David Airlie airl...@redhat.com wrote:
Also unless he rebuild the upstream mesa in rpm with the same flags, I'm
not sure
this is guaranteed fixed upstream.
Dave, for the sake of having the
On Fri, 2013-08-02 at 08:50 +0800, Morgan Howe wrote:
On Fri, Aug 2, 2013 at 8:38 AM, David Airlie airl...@redhat.com
wrote:
Also unless he rebuild the upstream mesa in rpm with the same
flags, I'm not sure
this is guaranteed fixed upstream.
I'd be happy to help
13 matches
Mail list logo
