| Summary: | Ren'Py gives X Error failed requiest after update to nvidia driver 470.129.06 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Martin Ward <martin> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | martin |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | x11-driver-video-nvidia-current-470.129.06 | CVE: | |
| Status comment: | |||
|
Description
Martin Ward
2022-07-16 11:58:05 CEST
Martin Ward
2022-07-16 11:58:50 CEST
CC:
(none) =>
martin Ren'Py is a third party app not provided by Mageia.
Please report this issue upstream at the developer site.
Can not reproduce this issue with dkms-nvidia-current-470.129.06-1.mga8.nonfree.x86_64.rpm and onsengame-1.50-linux.tar.bz2
on a GTX 1060
inxi -G
Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 470.129.06
Display: x11 server: Mageia X.org 1.20.14 driver: nvidia,v4l resolution: 1920x1080~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 470.129.06
Additionally onsengame-1.50-linux.tar.bz2 uses an old Ren'Py 7.4.6.1693 which has Python 2 support only. So this looks definitly like an upstream problem of your game developer or Ren'Py itself. You can see the used Ren'Py version in the log.txt of your game.
This is my graphics card:
inxi -G
Graphics: Device-1: NVIDIA GA104 [GeForce RTX 3070] driver: nvidia v: 470.94
Display: x11 server: Mageia X.org 1.20.14 driver: nvidia,v4l
resolution: 2560x1440~60Hz
OpenGL: renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2 v: 4.6.0 NVIDIA 470.94
Tested on my second machine with Nvidia and can't reproduce either:
inxi -G
Graphics: Device-1: NVIDIA GA102 [GeForce RTX 3080 Ti] driver: nvidia v: 470.129.06
Display: x11 server: Mageia X.org 1.20.14 driver: nvidia,v4l resolution: 1920x1080
OpenGL: renderer: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 470.129.06
According your comment 3 you are still using the old driver 470.94 . Did you properly restart your machine after update to 470.129.06-1 and did the kernel modules got build? I tested the driver update on a backup root partition, this is my main root partition which has not had the driver update applied. Is your complete main system that outdated? You are on 470.94 which got released in Mageia in Dec 2021!? - are your systems up to date at all (not only graphic card, also xorg, kernel, EVERYTHING)? - how old is your backup? - how do you test your backup (data integrity) - how do you work with your backups: in a virtual machine or on real HW? - which kernel are you using? And please don't mix output from your machines/backups/mains as it makes it more confusing. I normally keep everything up to date using mgaapplet. The nvidia driver was updated from 470.94 to 470.129.06 a few weeks ago and broke my renpy games, so I restored from my backup. Today I decided to try it again and report the problem. Everything else on my main partition, apart from the nvidia driver, is up to date: kernel-desktop-latest-5.15.50-1.mga8 x11-server-xorg-1.20.14-3.mga8 % cat /proc/version Linux version 5.15.50-desktop-1.mga8 (iurt@rabbit.mageia.org) (gcc (Mageia 10.3.0-2.mga8) 10.3.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Sat Jun 25 13:56:51 UTC 2022 I use rsync to keep the backup root partition up to date with the latest working main root partition and use grub to select which partition to boot from on power up. (In reply to Martin Ward from comment #8) > The nvidia driver was > updated from 470.94 to 470.129.06 a few weeks ago and broke my renpy games There is something fishy with your system...we have July 2022. nvidia-current-470.94-1.mga8 2021-12-22 nvidia-current-470.103.01-1.mga8 2022-02-12 nvidia-current-470.129.06-1.mga8 2022-05-16 I know I updated the kernel, and may have done the first nvidia update. Then I applied the latest updated and noticed the problem, so I restored from a backup which still had the previous kernel. It seems that this backup still had nvidia-current-470.94. I have since re-applied the kernel update, but when I tried the nvidia update it still has the problem. If you feel confident, you could try dkms-nvidia-current-510.73.05-1.mga8.nonfree.x86_64.rpm from nonfree_backports repository. Only make sure to remove backports media completely after your test or you could hit by bug 29830. Its easier to feel confident when you have backup root partitions :-) I tried it on a backup and it worked, so I have updated my main partition, and taken nonfree backports back off the sources list. Many thanks for your help and patience! :-) Installing dkms-nvidia-current-510.73.05-1.mga8.nonfree.x86_64.rpm from nonfree_backports fixes this Only make sure to remove backports media completely after your test or you could hit by bug 29830. Status:
NEW =>
RESOLVED |