Github messages for voidlinux
 help / color / mirror / Atom feed
From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Blender no longer working after update of the Nvidia Packages
Date: Mon, 13 Nov 2023 16:55:16 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47203@inbox.vuxu.org> (raw)

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

New issue by dataCobra on void-packages repository

https://github.com/void-linux/void-packages/issues/47203

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.11_1 x86_64 AuthenticAMD uptodate FFFFFF

### Package(s) Affected

blender-3.6.5_2, nvidia-535.129.03_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Blender is starting with the new version of Nvidia.

### Actual behaviour

Blender doesn't start and shows the following error:
```
Read prefs: "/home/datacobra/.var/app/org.blender.Blender/config/blender/3.6/config/userpref.blend"
Error! GLX_ARB_create_context not available.
Error! GLX_ARB_create_context not available.
Error! GLX_ARB_create_context not available.
Error! GLX_ARB_create_context not available.
Error! GLX_ARB_create_context not available.
Error! GLX_ARB_create_context not available.
Error! GLX_ARB_create_context not available.
Error! Unsupported graphics card or driver.
A graphics card and driver with support for OpenGL 3.3 or higher is required.
The program will now close.
```

### Steps to reproduce

1. Install Blender and Nvidia
2. Try to start Blender
3. Error will appear

             reply	other threads:[~2023-11-13 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 15:55 dataCobra [this message]
2023-11-13 16:38 ` [ISSUE] [CLOSED] " dataCobra
2023-11-13 16:38 ` dataCobra

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47203@inbox.vuxu.org \
    --to=datacobra@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).