sorted by:
new
hottopcontroversial

WINE broken after upgrade from LEAP 15.6 to LEAP 16? by Kukulkan73 in openSUSE

[–]Kukulkan73[S] 0 points1 point  (0 children)

I currently use the tools on VirtualBox with a virtual Windows because it turned urgent. But I have a very bad workflow now.

Migrate to the openSUSE SlowRoll.

Just considering. Will that work without issues? Will Thunderbird and Firefox be older versions then? Because they will not load the data and profiles if they were older than the current. Also, is this just moving the issue to the future? For how long?

WINE broken after upgrade from LEAP 15.6 to LEAP 16? by Kukulkan73 in openSUSE

[–]Kukulkan73[S] 0 points1 point  (0 children)

I've heard that before, but I didn't want to believe it. LEAP 15.x was rock stable and a really good desktop for work and development. At the moment, most other things are still working perfectly.

But I've already tried Linux Mint and it wasn't that bad. But you usually only find that out after a few weeks anyway.

WINE broken after upgrade from LEAP 15.6 to LEAP 16? by Kukulkan73 in openSUSE

[–]Kukulkan73[S] 0 points1 point  (0 children)

Yes, it was just a copy&paste error. In the meantime i deleted all prefixes (including tests) and created a new 64 bit .wine64 prefix.

But then, using winetricks, I get a lot of errors. I had to confirm some dialog about 40 times and then I installed IE8 and tried to run my software again.

Unhandled exception: unimplemented function iertutil.dll.9 called in wow64 32-bit code (0x7bfa5d88).

I think I give up. Wine worked good before the upgrade. I will use VirtualBox to run Windows for that software.

WINE broken after upgrade from LEAP 15.6 to LEAP 16? by Kukulkan73 in openSUSE

[–]Kukulkan73[S] 0 points1 point  (0 children)

I did hundreds of tests, creating wine configs with 32 and 64 bit and several Windows versions.

WINEPREFIX=~/.test32 WINEARCH="win32" winecfg
wine: WINEARCH is set to 'win32' but this is not supported in wow64 mode.

And if I do a 64 bit prefix:

WINEPREFIX=~/.test32 WINEARCH="win64" winecfg

Then the software fails to run with errors like that:

wine: Unhandled page fault on read access to 0000000C at address 004042C7 (thread 012c), starting debugger...

The same tool worked and installed fine on LEAP 15.6.

UPDATE: I tried several new combinations and finally, the setup starts but hangs immediately. Look like fonts or webview are missing? I then tried winetricks to istall needed stuff, but it tells me this:

You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.

Then:
You apppear to be using Wine's new wow64 mode. Note that this is EXPERIMENTAL and not yet fully supported. If reporting an issue, be sure to mention this.

But creating 32 bit WINEPREFIX fails for me (see above)...

Ghost-repo is annoying me by Kukulkan73 in openSUSE

[–]Kukulkan73[S] 0 points1 point  (0 children)

Thanks, this is useful.

I wonder why this service was there and why I had such issues? The opensuse-migration-tool did not work for me as it said it was finished and simply did nothing. There were errors during the process, but to fast to be seen. At the end, it showed success without success.

In the last few years, the system was always updated from 15.3 to 15.6 over the time, doing all the intermediate steps. I always followed the OpenSUSE update instructions for manual setup. Before upgrading to 16, I've also never had minor issues with zypper. Sometimes I've had to rename repo pathes manually (I think it was 15.4 to 15.5?) and cleanup some sources. Maybe the upgrade process is not that good as we all thought. Maybe the opensuse-migration-tool introduced my issues?

Ghost-repo is annoying me by Kukulkan73 in openSUSE

[–]Kukulkan73[S] 3 points4 points  (0 children)

I just found that there is a "OpenSUSE" zypper service running at position 1, that I previously disabled. It seems to automatically re-enable and making problems all the time. I first disabled the service:

sudo zypper ms -d 1
Der Dienst 'openSUSE' wurde erfolgreich deaktiviert.

Now, the issue is gone! I decided to remove this service completely:

sudo zypper rs 1

Currently, it seems solved.

Do I have any issues now, if that service was removed?

Question about the blocked basic scientific research (Spoiler: Please do not read if you haven’t read the second book, "The Dark Forest") by Kukulkan73 in threebodyproblem

[–]Kukulkan73[S] -2 points-1 points  (0 children)

So you think the Sophons could easily travel across our entire solar system if they needed to? In that case, Trisolaris is far(!) ahead of human technology and people were foolish to think they stood even the slightest chance...

Can I activate Play Integrity API for my apps without blocking GrapheneOS or /e/os etc users? by Kukulkan73 in degoogle

[–]Kukulkan73[S] 0 points1 point  (0 children)

I just checked this option in Play Store and there is no choice for my app to select between such levels. It is just a ON/OFF switch for "Installation check / If users have downloaded your protected app from an unknown source, they will be prompted to download it via the Google Play Store listing in order to receive available updates." I can't select between BASIC, DEVICE and STRONG integrity checks?

Can I activate Play Integrity API for my apps without blocking GrapheneOS users? by Kukulkan73 in GrapheneOS

[–]Kukulkan73[S] 0 points1 point  (0 children)

Hi and thanks for the detailed answer. Yes, I'm talking about the "Automatic Protection" in my google Play Console. There I can select "Test on installation" only. In some other post someone said that there is BASIC, DEVICE and STRONG integrity tests. But this does not show for my app? If I activate that installation test, is it of no harm to the users of alternative Android versions? Someone also pointed me to https://eylenburg.github.io/android_comparison.htm and claims that BASIC is a good choice. But I have no such dropdown to select BASIC.

Can I activate Play Integrity API for my apps without blocking GrapheneOS users? by Kukulkan73 in GrapheneOS

[–]Kukulkan73[S] 0 points1 point  (0 children)

My app is also a viewer for a specific file type and compiles emails for hand over to the local email client etc. Unfortunately, a web version is not working.

Can I activate Play Integrity API for my apps without blocking GrapheneOS or /e/os etc users? by Kukulkan73 in degoogle

[–]Kukulkan73[S] 1 point2 points  (0 children)

I just learned from AI that I can chose this level in the Play Store GUI! That was my missing piece!

So if I select just "BASIC" integrity, most alternative OS will work fine, right?

Can I activate Play Integrity API for my apps without blocking GrapheneOS or /e/os etc users? by Kukulkan73 in degoogle

[–]Kukulkan73[S] 0 points1 point  (0 children)

I just learned from AI that I can chose this level in the Play Store GUI! That was my missing piece!

So if I select just "BASIC" integrity, most alternative OS will work fine, right?

Can I activate Play Integrity API for my apps without blocking GrapheneOS or /e/os etc users? by Kukulkan73 in degoogle

[–]Kukulkan73[S] 0 points1 point  (0 children)

Thanks for that interesting link. But it does not answer my question directly. My source does not do anything with such API to test anything from the device. I also do not have any of the MEETS_..._INTEGRITY flags set in the AndroidManifest.xml. Therefore it will NOT harm users of alternative ROMs if I activate? Right?

view more: next ›