Thanks.
I have run updates multiple times a day for the past week hoping what you
are suggesting would transpire, but things are not getting fixed through a
simple update.
Here is the information requested:
$ dpkg -l libelf1 libelf1t64
dpkg-query: no packages found matching libelf1t64
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-===================================
ri libelf1:amd64 0.190-1+b1 amd64 library to read and write ELF
files
An attempt to install the 64 bit version of the library fails:
$ sudo apt-get install libelf1t64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
plasma-workspace : Depends: gdb-minimal but it is not going to be installed
or
gdb
Recommends: qml-module-org-kde-pipewire but it is not
going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused
by held packages.
Incidentally, I get the same error when I try to install the kernel headers
for kernel 6.7.7-amd64 (so I am not upgrading the kernel either). I was
trying that as a possible solution hoping that the newer kernel may have
fixed any problems of compatibility between nvidia-kernel and
linux-headers. No joy:
$ sudo apt-get install linux-headers-6.7.7-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
plasma-workspace : Depends: gdb-minimal but it is not going to be installed
or
gdb
Recommends: qml-module-org-kde-pipewire but it is not
going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused
by held packages.
The above error has also been persistent for the past 4-5 days.
Use of aptitude -f install for installation of kernel headers suggests that
I uninstall libelf:
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) linux-headers-6.7.7-amd64 [Not Installed]
Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:
Remove the following packages:
1) libcurl3-gnutls [8.6.0-3 (now, unstable)]
2) libdebuginfod1 [0.190-1+b1 (now, unstable)]
3) libdw1 [0.190-1+b1 (now, unstable)]
4) libelf1 [0.190-1+b1 (now, unstable)]
5) libnettle8 [3.9.1-2+b1 (now, unstable)]
Install the following packages:
6) libcurl3t64-gnutls [8.6.0-3.2 (unstable)]
7) libdebuginfod1t64 [0.190-1.1+b1 (unstable)]
8) libdw1t64 [0.190-1.1+b1 (unstable)]
9) libelf1t64 [0.190-1.1+b1 (unstable)]
10) libnettle8t64 [3.9.1-2.2 (unstable)]
11) linux-kbuild-6.7.7 [6.7.7-1 (unstable)]
Accept this solution? [Y/n/q/?]
So, I have a cluster of broken packages that are keeping me from fixing up
the situation through an update. From what you mention, maybe I have a
broken installation, but I have never seen a Debian installation break like
this through regular upgrades (I used to use Testing, but moved to Sid 3
years ago).
On Tue, Mar 12, 2024 at 6:31 PM Andreas Beckmann <a...@debian.org> wrote:
> That's the actual culprit:
>
> On 12/03/2024 13.33, JON Tauri wrote:
> > # LD [M] /var/lib/dkms/nvidia-current/525.147.05/build/nvidia-uvm.o
> > ld -m elf_x86_64 -z noexecstack --no-warn-rwx-segments -r -o
> > /var/lib/dkms/nvidia-current/525.147.05/build/nvidia-uvm.o
> > @/var/lib/dkms/nvidia-current/525.147.05/build/nvidia-uvm.mod ;
> > ./tools/objtool/objtool --hacks=jump_label --hacks=noinstr
> --hacks=skylake
> > --ibt --orc --retpoline --rethunk --sls --static-call --uaccess
> --prefix=16
> > --link --module
> /var/lib/dkms/nvidia-current/525.147.05/build/nvidia-uvm.o
> > ./tools/objtool/objtool: error while loading shared libraries:
> libelf.so.1:
> > cannot open shared object file: No such file or directory
> > make[4]: ***
> > [/usr/src/linux-headers-6.6.15-common/scripts/Makefile.build:443:
> > /var/lib/dkms/nvidia-current/525.147.05/build/nvidia.o] Error 127
> > make[4]: *** Deleting file
> > '/var/lib/dkms/nvidia-current/525.147.05/build/nvidia.o'
> > make[4]: *** Waiting for unfinished jobs....
>
> This is not a bug in nvidia-kernel-dkms.
> I assume this is a temporary breakage due to the ongoing 64-bit time_t
> transition which involves a huge amount of package renames.
>
> I cannot reproduce it in an up-to-date sid chroot with
> linux-headers-6.6.15-amd64 installed (which has been superseded by 6.7.*
> btw).
>
> Updating your system again should probably fix the issue.
>
> In case it persists: Which variant and version of the libelf.so.1
> library do you have installed?
>
> dpkg -l libelf1 libelf1t64
>
>
> Andreas
>
