Open psyciknz opened 1 year ago
Funny you posted this, I just set up this container and have the same issue happening to me as well. I also excluded all of those folders anyway, not sure if that matters since I am assuming this has to do with Backblaze writing their reports of uploaded files to the drive
Just background the window and ignore it. Everything seems to work fine.
On Tue, Sep 12, 2023 at 8:38 PM NinFanBoyFTW @.***> wrote:
Funny you posted this, I just set up this container and have the same issue happening to me as well. I also excluded all of those folders anyway, not sure if that matters since I am assuming this has to do with Backblaze writing their reports of uploaded files to the drive
— Reply to this email directly, view it on GitHub https://github.com/JonathanTreffler/backblaze-personal-wine-container/issues/70#issuecomment-1716891902, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLQM6AYW636S3PTSTTVFYLX2ETFBANCNFSM6AAAAAA4VW4HKU . You are receiving this because you are subscribed to this thread.Message ID: <JonathanTreffler/backblaze-personal-wine-container/issues/70/1716891902@ github.com>
+1 for this issue on an install from 2 days ago. Everything works fine, so just a minor annoyance that it keeps popping up
I too am getting this warning/error every time I open the container.
I guess this is just some error in the Backblaze application which was definetely not made for this kind of usage. I am backing up with this container since version 1.0 (2022) and this error pops up every now and then and can - in my opinion - be ignored. However, I didn't have the time (yet) to investigate further. All my numerous backup/restore tests were successful, so the backup itself is not impacted.
Been happening to me since I started using this a year ago...
+1 for me too
I experience the same issue, backup's running fine though.
I experience the same issue, backup's running fine though.
thats good. And as I mentioned, you can ignore ther error. Backblaze was not made to be working well with Wine.
Hello! Same issue, brand new user of the container.
I know we can ignore, but it doesn't look like "clean". Is there something we can do to avoid this popup to show?
Seems related to this https://github.com/JonathanTreffler/backblaze-personal-wine-container/issues/53
So having an issue I can't seem to resolve.....I don;t think it causes an impact, but an annoyance with a popup over the screen.
You can see from the command window that /config/wine/c_drive/ProgramData/Backblaze/bzdata/bzreports has 777 permissions. But I still seem to get the error.
Is the command window path the actual path it is having a problem with, or is it somewhere else in teh container.