unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Chris Lemmer-Webber <cwebber@dustycloud.org>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: help-guix@gnu.org
Subject: Re: Blender freezes i3wm
Date: Thu, 24 Jun 2021 14:32:51 -0400	[thread overview]
Message-ID: <87sg17qfjg.fsf@dustycloud.org> (raw)
In-Reply-To: <874kdnb5k4.fsf@dustycloud.org>

Spoke too soon, unfortunately. :\

My whole desktop still crashed after some period of use.  However, let
me give some better news...  the patch I linked is not yet in the latest
version of Blender we ship.  So this can probably be fixed either by
upgrading Blender or, should that be annoying to do temporarily, by
backporting this patch, which merges quite cleanly.

Chris Lemmer-Webber writes:

> I've had the same issue.  I think for me at least, here's the relevant
> issue:
>
>   https://developer.blender.org/T72902
>
> Apparently if someone encounters other issues with their card, these
> need to be added "on a case per case basis"
>
>   https://developer.blender.org/rBb7acb8690a4d189868c6e0b57057b6fcd8a5a96d
>
> However adding new cards doesn't look too hard.
>
> Not sure if this is too helpful to anyone but I suspect this might keep
> happening with intel cards as they roll out.
>
> Ekaitz Zarraga writes:
>
>> Weirdly enough, yesterday I sculpted for 2h in a row and everything
>> went well.
>>
>> After that, I opened the model I worked on and it freezed my screen
>> again, but this time some buttons of other screens started to appear
>> on top of the frozen window.
>>
>> Very weird.
>>
>> Anyway, this looks like it's impossible to debug so I'm going to act
>> as it didn't happen.



  reply	other threads:[~2021-06-24 18:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 17:40 Blender freezes i3wm Ekaitz Zarraga
2021-03-19  1:24 ` raingloom
2021-03-19 12:49   ` Ekaitz Zarraga
2021-03-19 16:00     ` raingloom
2021-03-27  1:09       ` Ekaitz Zarraga
2021-03-27 12:07         ` Ekaitz Zarraga
2021-03-27 14:45         ` Luis Felipe
2021-03-27 19:33           ` Luis Felipe
2021-03-27 21:31             ` Ekaitz Zarraga
2021-03-29  9:36               ` Ekaitz Zarraga
2021-06-24 16:17                 ` Chris Lemmer-Webber
2021-06-24 18:32                   ` Chris Lemmer-Webber [this message]
2021-06-25 17:49                     ` Chris Lemmer-Webber
  -- strict thread matches above, loose matches on Subject: below --
2021-10-03 19:59 Ekaitz Zarraga
2021-10-03 20:40 ` Leo Famulari
2021-10-03 20:47   ` Ekaitz Zarraga

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87sg17qfjg.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=ekaitz@elenq.tech \
    --cc=help-guix@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).