Wine stopped working after jumping to the future and back

arcanedarkness · 2021-11-01 16:18:47

I lost my patience at a clicker game and I used timedatectl to change the date of my system to 10 years in the future, reap the rewards in the clicker game, and then jump back to the current date. The problem is, after I jumped back to the current date wine stopped working at all with the following error message:

wine: error while loading shared libraries: libpthread.so.0: cannot stat shared object: Error 75

I found that wine (and other applications open at the time) created some files with the date in the future with:

find .. -mtime -0 -exec stat {} \;

I tried to fix it with (the -h was used because some files are symbolic links to terminals):

find .. -mtime -0 -exec touch -h {} \;

The problem is: this did not update the Birth (crtime) of the files (that exists in EXT4 but does not seem to be fully supported by POSIX). The problem remains, and the worse is that I cannot find the files anymore because find is not able to search for the creation time (-ctime searches for change time). Someone has any tips on how to proceed?

seth · 2021-11-01 16:33:03

Do you still have the find results in the console buffer?
Copying them off the FS (eg. /tmp tempfs), deleting the original file and copying the copy in /tmp will pretty much sanitize all timestamps w/o the need for debugfs.

Maniaxx · 2021-11-01 16:47:52

Did you restart the system already after resetting the time?
These might be just broken file handles.

Last edited by Maniaxx (2021-11-01 16:55:04)

arcanedarkness · 2021-11-01 17:24:20

@seth

Unfortunately I checked the man page of find in the same terminal and I think this has overwrite the results.

@Maniaxx

I did restart the computer (this happened yesterday, and I turn off the computer while I sleep). I remember that many of the broken wine files were symbolic links to /dev/stty* (i think the links themselves were called "com" or "comm"). This also complicates my life because I probably need to take some care when trying to copy from and copy back to fix these symbolic links, otherwise it will try to copy the pointed devices instead.

Maniaxx · 2021-11-01 17:36:44

What about reinstalling wine?

arcanedarkness · 2021-11-01 18:40:06

I will do it and report back. However, I think the problem is in the ~/.wine directory because wine was run without sudo, and I would like to keep .wine as it is (except by the wrong dates), as well as fix possible problem in other applications that did not explode yet.

arcanedarkness · 2021-11-01 18:42:10

The reinstall did not solve the problem but had an interesting result:

$ sudo pacman -U /var/cache/pacman/pkg/wine-6.10-1-x86_64.pkg.tar.zst
loading packages...
warning: wine-6.10-1 is up to date -- reinstalling
resolving dependencies...

looking for conflicting packages...

Packages (1) wine-6.10-1

Total Installed Size:  453.51 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                      [###########################] 100%
(1/1) checking package integrity                    [###########################] 100%
(1/1) loading package files                         [###########################] 100%
(1/1) checking for file conflicts                   [###########################] 100%
(1/1) checking available disk space                 [###########################] 100%
:: Processing package changes...
(1/1) reinstalling wine                             [###########################] 100%
:: Running post-transaction hooks...
(1/5) Registering binary formats...
(2/5) Arming ConditionNeedsUpdate...
(3/5) Updating fontconfig cache...
(4/5) Updating 32-bit fontconfig cache...
/usr/bin/fc-cache-32: error while loading shared libraries: libpthread.so.0: cannot stat shared object: Error 75
error: command failed to execute correctly
(5/5) Updating the desktop file MIME type cache..

Maniaxx · 2021-11-01 18:59:15

You could (temporarily) create/test another wine prefix/folder.

Also try this to tackle the libpthread.so problem:

sudo pacman -S glibc

If this doesn't help post this output:

$ stat /usr/lib/libpthread.so.0
$ stat -L /usr/lib/libpthread.so.0

Last edited by Maniaxx (2021-11-01 19:02:05)

arcanedarkness · 2021-11-01 19:20:19

I think I was able to solve the problem. The problem was that the access time of the /usr/lib32/libpthread.so.0 and the /usr/lib/libpthread.so.0 became "2041-10-31 23:53:01.340006916 -0300" (the other were not modified, as expected, as wine did not run with sudo and could make not changes).

After this I had a problem with /etc/hosts was being ignored (a DNS problem), and it was solved by just calling sudo systemctl restart nscd.service; it seems nscd (my DNS cache) also got confused by the time change.

Good to know the system can end up messed up in this kind of play (going to the future and back), I need to remember to avoid this in the future.

Arch Linux

#1 2021-11-01 16:18:47

Wine stopped working after jumping to the future and back

#2 2021-11-01 16:33:03

Re: Wine stopped working after jumping to the future and back

#3 2021-11-01 16:47:52

Re: Wine stopped working after jumping to the future and back

#4 2021-11-01 17:24:20

Re: Wine stopped working after jumping to the future and back

#5 2021-11-01 17:36:44

Re: Wine stopped working after jumping to the future and back

#6 2021-11-01 18:40:06

Re: Wine stopped working after jumping to the future and back

#7 2021-11-01 18:42:10

Re: Wine stopped working after jumping to the future and back

#8 2021-11-01 18:59:15

Re: Wine stopped working after jumping to the future and back

#9 2021-11-01 19:20:19

Re: Wine stopped working after jumping to the future and back

Board footer