-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"cabal update" failing with "fdLock: invalid argument" (v1- and v2-) #7442
Comments
During the past week, this was the temporary fix I used:
This works, but I'd like to be able to update without resorting to using another device. |
There is a series of issues that, I think, duplicate this one. In particular, taking the binary from here should probably fix this issue for you: Here is the upstream issue (work around a glibc bug?) that is probably not being work on, because of lack of i386 machine to test. I think originally this is a glibc bug, so in a few years it should be fixed in your distro, I guess. |
duplicate of #7313 EDIT: It did not work, i guess due to permission over the repo, but it should work for you @Mikolaj |
duplicate of #7313? |
Duplicate of #7313 |
Would you believe it, capitalisation makes a difference. :D |
Closing as a dup |
cabal update
is failing withfdLock: invalid argument (Invalid argument)
. This is happening to bothv1-
andv2-
.Reproducing with
v1-update
Due to this issue I am not being able to install anything via cabal on my device. Cabal fails to "download-and-unpack" the package database:
Reproducing with
v2-update
Due to this issue I am not being able to install anything via cabal on my device. Cabal fails to "download-and-unpack" the package database:
System information
Using
-v
32-bit system issue?
My system is 32 bit, see:
This may or may not be related to the problem, see:
The
l_len
argument above seems to have a suspicious 64-bit value...64-bit works
Running the same v1-update / v2-update commands on my 64-bit box running Arch Linux works fine (Linux 5.10.6, GHC 8.10.4, cabal-install v3.2.0.0 and cabal-lib v3.2.1.0).
Fresh user
Just to be safe, I also replicated the bug on a fresh user with an empty home directory. Cabal still fails in the same way.
The text was updated successfully, but these errors were encountered: