u/Kukulkan73

Hi. I used Plasticity with OpenSUSE 15.6 without issues. Yesterday I upgraded to LEAP 16 because 15.6 is EOL. Since then, Plasticity screen stays black. I need to mention, that the new version only supports Wayland while previous versions were on X11.

I then tried to install a more recent version of plasticity as my license runs until May 2026. No success. I tried several ELECTRON flags and parameters, but no success. Basically it is always this error:

> Plasticity
14:56:36.091 › MAIN: Process starting...
14:56:36.261 › MAIN: Application version 26.1.3
14:56:36.264 › MAIN: ...Process started
14:56:36.308 › MAIN: App ready
loading file:///usr/lib/Plasticity/resources/app/.webpack/renderer/app_window/index.html file:///usr/lib/Plasticity/resources/app/.webpack/renderer/app_window/index.html
14:56:36.622 › RENDER: Process starting...
14:56:36.630 › RENDER: License validity: true
(node:142747) UnhandledPromiseRejectionWarning: Error: ERR_FAILED (-2) loading 'file:///usr/lib/Plasticity/resources/app/.webpack/renderer/app_window/index.html'
   at rejectAndCleanup (node:electron/js2c/browser_init:2:85498)
   at WebContents.stopLoadingListener (node:electron/js2c/browser_init:2:85885)
   at WebContents.emit (node:events:513:28)
(Use \Plasticity --trace-warnings ...` to show where the warning was created)(node:142747) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)14:56:37.525 › MAIN: Render process gone { reason: 'crashed', exitCode: 134 }^(C14:56:49.572) › MAIN: Main window closed`

The file exists:

> ll /usr/lib/Plasticity/resources/app/.webpack/renderer/app_window/index.html
-rw-r--r-- 1 root root 364 20. Apr 16:36 /usr/lib/Plasticity/resources/app/.webpack/renderer/app_window/index.html

It is readable by my user without issues. I have neither AppAmor nor SELinux activated.

Now, after a few more tries with several versions, it stopped poducing the above error and I get this instead:

> Plasticity  
15:14:56.717 › MAIN: Process starting...
15:14:56.881 › MAIN: Lock taken

What's going on? What lock? Maybe a crash left some temp files that I need to delete?

EDIT: Please note that I'm not on Discord!

Hi. I previously used wine to run two Windows tools on LEAP 15.3 to 15.6. But after the LEAP 16.0 upgrade yesterday, nothing works anymore with wine. I tried to wipe all wine from the machine and re-installed wine, wine-gecko, wine-mono and winetricks.

I also installed grub2-compat-ia32 package, because I found that somewhere on an OpenSUSE site. I also installed glibc-32bit, libstdc++6-32bit, libgcc_s1-32bit. But, no matter what I try, with several Windows software, I always get this error:

> wine --version
wine-10.10

> wine Setup.exe
00b8:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b8:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b8:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b8:fixme:wineusb:query_id Unhandled ID query type 0x5.
012c:err:environ:init_peb starting L"Z:\\home\\kukulkan\\dummy\\pp_pro\\Setup.exe" in experimental wow64 mode
wine: could not load kernel32.dll, status c0000135

I then tried with three other softwares and the error is always exactly the same.

Then I tried to follow the advise of AI to use wine as flatpack:

> flatpak run org.winehq.Wine Setup.exe
002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2).
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: File not found.

So this is also not working at all. I did hundreds of tests, creating wine configs with 32 and 64 bit and several Windows versions. This is, in addition, very confusing. I encountered tons of error messages about wow64 and whatever, but nothing helped me to get it run.

I then tried to use bottles as flatpack, but it simply did nothing when I tried to run anything in there. I did not even find a log or some report about whats going on. I immediately removed bottles, as I don't like software hiding whats going on and what the error was. Doing nothing with no output at all is unacceptable. And no, the three dots on top did not show an option to see logs...

I come to the conclusion, that using WINE is impossible with OpeneSUSE LEAP 16 now?

UPDATE:

I gave up. Since yesterday, I spent about 5 hours now trying to let the Windows tools, I used in LEAP 15.x, work in the new version LEAP 16. This is a work machine, I have no time to spend on such. I just decided to use a Windows VM in VirtualBox to run that software. Unfortunately , bad integration, but I have no choice. I need that to get running now.

Hi,

I recently upgraded from LEAP 15.6 to 16.0 and since then, I can't update any longer:

sudo zypper up
Dienst 'openSUSE' wird aktualisiert.
Unerwartete Ausnahme.
[openSUSE:repo-oss|http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/x86_64] Repository already exists.
Senden Sie einen Fehlerbericht zu diesem Problem.
Anweisungen finden Sie unter http://de.opensuse.org/Zypper/Fehlersuche.

But this repo URL does not even exist?

zypper lr -u
Die Repository-Prioritäten sind ohne Effekt. Alle aktivierten Repositorys teilen sich die gleiche Priorität.

# | Alias | Name | Enabled | GPG Check | Refresh | URI

--+--------------------------------------+-----------------------+---------+-----------+---------+------------------------------------------------------------------------

1 | WINE_current | WINE current | Nein | ---- | ---- | https://download.opensuse.org/repositories/Emulators:/Wine/16.0/

2 | code | Visual Studio Code | Nein | ---- | ---- | https://packages.microsoft.com/yumrepos/vscode

3 | http-ftp.gwdg.de-9cf0fd5b | Packman Repository | Nein | ---- | ---- | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_16.0/

4 | http-opensuse-guide.org-c26d2681 | libdvdcss repository | Nein | ---- | ---- | http://opensuse-guide.org/repo/openSUSE_Leap_16.0/

5 | https-download.opensuse.org-98e5c373 | Office | Nein | ---- | ---- | https://download.opensuse.org/repositories/Office/SLE_15_SP2_Backports/

6 | microsoft-edge | microsoft-edge | Nein | ---- | ---- | https://packages.microsoft.com/yumrepos/edge/

7 | openSUSE:repo-non-oss | openSUSE:repo-non-oss | Ja | (r ) Ja | Ja | http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss

8 | openSUSE:repo-openh264 | repo-openh264 (16.0) | Ja | (r ) Ja | Ja | http://codecs.opensuse.org/openh264/openSUSE_Leap_16

9 | openSUSE:repo-oss | openSUSE:repo-oss | Ja | (r ) Ja | Ja | http://cdn.opensuse.org/distribution/leap/16.0/repo/oss

Zypper refresh does not trigger any error and also not showing that url:

sudo zypper refresh

Es wird nach gpg-Schlüsseln im Repository openSUSE:repo-non-oss gesucht.
 gpgkey=http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss/repodata/repomd.xml.key
Metadaten von Repository 'openSUSE:repo-non-oss' abrufen ......................................................................................................................[fertig]
Cache für Repository 'openSUSE:repo-non-oss' erzeugen .........................................................................................................................[fertig]
Es wird nach gpg-Schlüsseln im Repository repo-openh264 (16.0) gesucht.
 gpgkey=https://codecs.opensuse.org/openh264/openSUSE_Leap_16/repodata/repomd.xml.key
Metadaten von Repository 'repo-openh264 (16.0)' abrufen .......................................................................................................................[fertig]
Cache für Repository 'repo-openh264 (16.0)' erzeugen ..........................................................................................................................[fertig]
Es wird nach gpg-Schlüsseln im Repository openSUSE:repo-oss gesucht.
 gpgkey=http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/repodata/repomd.xml.key
Metadaten von Repository 'openSUSE:repo-oss' abrufen ..........................................................................................................................[fertig]
Cache für Repository 'openSUSE:repo-oss' erzeugen .............................................................................................................................[fertig]
Alle Repositorys wurden aktualisiert.

How to get rid of that ghost-repo?