Package: nvidia-legacy-340xx-driver
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
The ts contacted me and said that the symlink does not work.
Since last time, we had another, bigger flood that caused even more damage, and
I do not know if I will have the gt210 by Christmas so
On 21/09/2023 11.38, jim_p wrote:
First and foremost, sorry for not replying earlier and for not testing the glx
symlink as proposed. The storms, the floods and the power outages that happened
here the first days of September caused enough damage to my hardware that
forced me to make more
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
First and foremost, sorry for not replying earlier and for not testing the glx
symlink as proposed. The storms, the floods and the power outages that happened
here the first days of September
On 30/06/2023 15.39, Andreas Beckmann wrote:
Could you try
ln -sf libGL.so.1 /usr/lib/x86_64-linux-gnu/libGLX.so.0
(assuming amd64) and see if that fixes Qt5 operation? Or breaks other
stuff?
Did you already find some time to test this?
Andreas
On 04/07/2023 11.51, jim_p wrote:
That lib is part of mesa's libglx0, which brings me to another serious question
I had forgotten for almost a decade. If the system does not use mesa's libs for
anything, because it uses nvidia's libs, why must it have them installed?
If GLVND is used (e.g. all
On 04/07/2023 11.51, jim_p wrote:
But enough with the rant. I want to try what you suggested with the symlink,
but I want to know the procedure to undo it. Btw, the file is already symlinked
to some other lib
$ file /usr/lib/x86_64-linux-gnu/libGLX.so.0
/usr/lib/x86_64-linux-gnu/libGLX.so.0:
Package: nvidia-legacy-340xx-driver
Version: 340.108-19
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Last century's? The tesla (nv50) family was release near the end of the 2010's
decade and it, luckily, had full support by nvidia until the end of 2019! And
since then, it is
Control: reopen -1
On 29/06/2023 18.16, jim_p wrote:
So, can a patch like the one for kodi be applied to qt5? I am mentioning again
that arch does not have a seperate -gles package for qt5, so a single lib that
works everywhere should be possible.
It's unlikely to convince the Qt5 maintainers
Package: nvidia-legacy-340xx-driver
Version: 340.108-19
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Kodi, with today's release of 20.2, fixed the gl library issue with this commit
here
https://github.com/xbmc/xbmc/pull/23226
In other news, a few days ago, qbittorrent became
Package: nvidia-legacy-340xx-driver
Version: 340.108-18
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Honest question to the maintainers, and to the qt5 maintainers too:
What if someone wants to install/run a package that explicitly depends on
libqt5gui5?
I wanted to try
Package: nvidia-legacy-340xx-driver
Version: 340.108-18
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
I contacted an arch user who still uses nvidia 340 from aur and, as he mentions
in the comments, there is no issue with qt5 apps and nvidia 340 there.
I do not know how arch
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Thank you for the clarifications. No offence, but as you described it, this is
practically "planned obsolescence in the opensouce world". Ok, the 340 driver
is old and it does
Control: tag -1 upstream wontfix
On 11/02/2023 12.23, jim_p wrote:
Some manjaro user from github found a solution for kodi v20. Launching it like
so makes it work, so this probably means that kodi v20, unlike v19, does not
detect the library properly.
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Some manjaro user from github found a solution for kodi v20. Launching it like
so makes it work, so this probably means that kodi v20, unlike v19, does not
detect the library
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Please excuse me if I have already said anything of the following and I am now
repeating myself. I have so much in my mind that sometimes I forget what I said
a couple of days
On 09/02/2023 13.10, jim_p wrote:
According to these reports that come from ubuntu, mint and arch, kodi 20 has
the same issue with the nvidia 340 driver, regardless of kernel and xorg
version. Thus, I think it can now be ignored when troubleshooting the issue
mentioned here.
The only thing I
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
According to these reports that come from ubuntu, mint and arch, kodi 20 has
the same issue with the nvidia 340 driver, regardless of kernel and xorg
version. Thus, I think it
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Sorry but no, I can not trace it to something specific. Everything was working
fine on 6.0 and -16, but they are like 2 months old now. I have very few qt
apps and I rarely use
On 05/02/2023 16.58, jim_p wrote:
- I rebooted and ran kitty, but the issue is still there
And after all that I reinstalled -17 :'(
Thanks for testing. So it's maybe the kernel module ...
Do you remember the last working configuration?
Andreas
On 05/02/2023 16.36, jim_p wrote:
I have already backed up the patch file on my dekstop. If I install -16 from
snapshot.d.o, dkms will rebuild the driver right after apt installs it and it
will fail. I will then move the patch to the right folder, replacing the one
from -16. How will I force
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Ok I just did it, but nothing changed. In detail:
- I installed -16 from snapshot
- I let dkms fail to build the driver and apt/dpkg with its failed exit status
- I moved the
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Please help me on that...
I have already backed up the patch file on my dekstop. If I install -16 from
snapshot.d.o, dkms will rebuild the driver right after apt installs it and
Did you try nvidia-legacy-340xx-kernel-dkms -16 (get it from
snapshot.d.o) with only the use-nv-kernel-ARCH.o_binary.patch patch
replaced by the version from -17 to get support for Linux 6.1?
That gives you again the older set of acpi patches.
If that works I'll look again into the acpi patches
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
First of all, the title should be "gl related apps fail to launch" and let me
explain why.
I tried libreelec 11 beta 1 which came out a few days ago. It uses kernel 6.1,
nvidia
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
How can I install 6.0 alongside -16 to test if it works with qt5 5.15.8 and
kodi 20? Installing 6.0 is easy, installing -16 is easy too. The problem is
that when I install -16,
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Goodmorning. Before I start, I would like to say that yesterday I completely
missed message #27 above and that I am really sorry for that useless wall of
text that reportbug
On 26/01/2023 19.30, jim_p wrote:
As for the patches, there is no 0042 patch, neither as a file from nvidia-
Yep, 0042 is for Linux 6.2 and currently only in sid.
As for getting the -16 version from snapshot.d.o. I think it will be hard to
get all the correct packages that are derived from
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Thank you for all that info.
Please allow me to check the -dbgsym packages and post a new strace the
following days. It is something new for me and I will probably make a mess
On 26/01/2023 18.50, Andreas Beckmann wrote:
On 26/01/2023 18.24, jim_p wrote:
And all that happened after the upgrade to 6.1 AND the driver's update
to the
-17 version, which the one that made it compatible with 6.1. There
were ZERO
No patches are needed for 6.1, only for 6.2.
Nonsense, I
On 26/01/2023 18.24, jim_p wrote:
we all know it is related to some gl lib not loading. Here is a coredump debug
if you want to check
https://paste.debian.net/1268410/
libc6-dbgsym, kodi-dbgsym might make the backtrace more informative.
And all that happened after the upgrade to 6.1 AND the
Control: tag -1 upstream wontfix
On 26/01/2023 11.46, George4X via pkg-nvidia-devel wrote:
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
All Qt5 apps fail to launch with a segfault
The 340xx legacy driver is EoL for several years only and does not
support current Xorg (only with
31 matches
Mail list logo
