/opt folder missing about pi-apps HOT 13 CLOSED

Hello there 👋
Thanks for submitting your first issue to the Pi-Apps project! We'll try to get back to you as soon as possible.
In the meantime, we encourage you join our Discord server, where you can ask any questions you might have.

Please respond as soon as possible if a Pi-Apps maintainer requests more information from you. Stale issues will be closed after a lengthy period of time with no response.

from pi-apps.

Thanks for reporting. I just got finished looking at this same report that you sent in using the 'send report' button.
In this case, it looks like the cause of your issues is that a system folder is missing /opt/. Do you remember deleting that folder?

We have had users report a missing /opt folder before, so to fix it, a one-time repair command was added to pi-apps that checks for a missing /opt/ folder and adds creates it if missing. In your case the folder must have been removed after that one-time repair check was run, or something else went wrong.

Long story short, try running this command to create the missing /opt folder:

sudo mkdir /opt

This should solve the issue. After running that command, please retry installing Wine.

from pi-apps.

Hello, thank you for your help. So i dont remember deleting opt folder, but when i added it there, it worked and i sucesfully installed Wine64 on my raspberry pi. Thank you very much for your help.

from pi-apps.

@FrenZy931 can you upload or paste the contents of the file ~/pi-apps/data/runonce_hashes

With that file's contents I can check to make sure that the runonce that corrects /opt actually did run at some point in the past.

from pi-apps.

So, for some reason, i cant upload the file, but i will paste it:

19637fcc657af32d1b834e920bc54ee72f2b3076
d0de63dc3a6f0861fd29a61b772a1ce36f349ba8
4fc1fdfcc760e68d067f1bb9af22822393bfef0a
e1a455d3be745b9cb033c0d053532142b08fbc24
50a13d1138fca812c87131f8cda23d31762b1f6b
df7ad95f0e073fd66c146647cba094e9c66b2dc0
dfb57ecc75c43daf7c4592a1115f59ad5f04856d
88fea75739686e3bad8c5aa64f48bc913f188176
e48bf347e7d32a0a3149c3214fe124ccf1b77543
084bb057834363ce504ae6736c8abefaf82fa702
604f470e06084647eff30fe8a490a35e2ac7a751
65fc6637314ef4b072cfd87fdc3a6b561a2e1f09
9abe286d42630496e396750937ae31b4ae0df344
32257dab359557af25997b1dab042419e4c53cfb
3174f1fa3a14435eebd575d3c7f705ca80561bbe
34c4034ed9d04ac3f720faf452bc6a45ddc4b354
534195dab8025e28a6944508f79800d53a855f13
56963e4d7e55f079dcd6848682014a3bb97fbdc2
48e310f63054e8a5cc68f7280b96d71d19f1bc22
e5b75857d869a68bb1f5a84fcf8e97835a85ae6a
38510f22af0071c519799f3f177406c78b2832d9
8118c1f1e686fa42555188da47a769ceb6475f70

I hope this is what you need, becouse i have no idea what this is

from pi-apps.

The 19637fcc657af32d1b834e920bc54ee72f2b3076 hash is a record indicating that the one-time fix to create the /opt folder has already been completed.
This indicates that your /opt folder mysteriously disappeared after you installed Pi-Apps.

from pi-apps.

Not necessarily. While the runonce did complete it does not exit on individual command failure.
It's possible that
sudo_popup mkdir /opt failed due to the user closing out of password prompts.

In a new terminal can you please paste and run

DIRECTORY=~/pi-apps source ~/pi-apps/api source
sudo_popup echo test

Edited by botspot to actually test sudo_popup (earlier it was defining a sudo_popup function but then running plain sudo)

from pi-apps.

@FrenZy931, have you had a chance to try the command we asked you to try? This is important and without a response we cannot make further progress.

from pi-apps.

I am unable to reproduce any issue on my end. sudo_popup works correctly with passwordless sudo and sudo where a password is required and a popup requests the users password.

It is possible that the user hit cancel on the password prompt. The way this runonce is structured, it will NOT exit and error code on individual command failures.

from pi-apps.

Hello, sorry but i wasnt home for 4 days, and i didn't had access to internet. I will run the comnand right when i will get back to my raspberry pi.

from pi-apps.

While updating Wine today, the process stuck with the window 'The Wine configuration in E:\home\pi.wine is being updated, please wait...'. The message 'err:system:update_display_cache Failed to read display config' is showing perpetually.
System: Pi OS 64 Bullseye on a Pi400
I have the same issue on Pi OS 64 Buster on a Pi4 8gb (I know, not supported anymore). After breaking the process the desktop turns black (toolbar still ok). Can't restore the desktop, not even after cold reboot. System hangs.

from pi-apps.

While updating Wine today, the process stuck with the window 'The Wine configuration in E:\home\pi.wine is being updated, please wait...'. The message 'err:system:update_display_cache Failed to read display config' is showing perpetually. System: Pi OS 64 Bullseye on a Pi400 I have the same issue on Pi OS 64 Buster on a Pi4 8gb (I know, not supported anymore). After breaking the process the desktop turns black (toolbar still ok). Can't restore the desktop, not even after cold reboot. System hangs.

this is unrelated to this issue.

Regardless it is a box64 bug that affects all wine versions ptitSeb/box64#1031 . it might be fixed in box64 master branch as of a few hours ago but we are waiting on the build here https://github.com/Pi-Apps-Coders/box64-debs/actions/runs/6667145327 to finish

from pi-apps.

Hello, sorry but i wasnt home for 4 days, and i didn't had access to internet. I will run the comnand right when i will get back to my raspberry pi.

@FrenZy931 bump

from pi-apps.