Myrlyn / Discover differences

English Install/Boot/Login
1

When installing wine, I saw q4wine was listed in Myrlyn, and then not. I think I either did a refresh or by looking in Discover. In Discover, Flatpak had it. So I installed wine in Myrlyn and then q4wine with flatpak. I have not finished the set up yet, as it’s asking questions.

Now today, in discover, Flatpak has an update for org.winehq.Wine.gecko and org.winehq.Wine.mono as refresh of version stable-25.08. But Myrlyn doesn’t have any update of mono 10.1.0-lp160.3.1 nor gecko 2.47.4-bp160.1.2.
What should I do? Is Flatpak using the wine I installed or did it install it’s own?

Also, the questions q4wine is asking is for the binaries. The defaults are /app/bin/wine, etc… But there is no /app folder. I don’t understand how flatpak works, as is a there a hidden set of /app folders in flatpak? Do I need to change it to /usr/bin/wine ?

1 Like
2

Flatpaks are self-contained (or use their own libraries where there are dependencies), so it doesn’t use the system libraries at all.

Myrlyn doesn’t, as far as I know, do anything with flatpaks.

The paths you’re seeing in flatpak-installed apps are within the flatpak itself.

1 Like
3

So I finished the setup and left everything to the /app defaults. When I try to run winecfg, etc., they exit with a code of -1. Looking in the log, I copy the exec string and run it in a terminal and it says
/bin/sh: line 1: /app/bin/wine: No such file or directory
If I shouldn’t use Myrlyn, where should I point the binaries to?

4

What is the exec string that you’re using?

The path /app/bin/wine is inside the flatpak, not outside it, so it won’t work outside the flatpak.

5

if you’re using flatpaks, launching them from the terminal would be done with flatpak run org.winehq.Wine --command winecfg or something similar.

(I don’t know the actual command)

1 Like
6

I was running it as the default setup of q4wine.

7

I don’t have it installed - but showing what you actually included would be helpful.

8

Installing a combo of Flatpack and regularpackages is probably a not good idea

9

I’d call that nonsense. Flatpaks live isolated from system packages.

2 Likes
10

^^ Agreed - pick and choose according to requirements and availability.

11

I installed wine from Myrlyn and when I no longer saw q4wine there, I looked in Discover. It had asked me about the binary directories during setup. I held off until hearing they have isolated systems, and then all I did was hit Next, Next, Next, etc. to the end.

When looking through q4wine now, I cannot find those settings. I do find similar things set as /app such as in the Utils tab for console binary: /app/bin/konsole
I’m not sure what to do at this point. It looks like it took the default input and set up defaults for the wine instance and can’t go back to change it other than changing each icon of the wine instance.

Is there a way to find out whether the q4wine installed wine or other things?
I hadn’t used flatpaks before because I didn’t understand them.

12

I found it. In Prefixes of the default instance, clicking the tools icon, it shows

Binary: /app/bin/wine
Server: /app/bin/wineserver
Loader: /app/bin/wine

Which of course don’t exist on my main system, but does it somehow exist (or supposed to exist) in this flatpak system?

And today, Discover is wanting to update KDE Application Platform in flatpak. Is that right? I thought KDE was in the main system?

To me, not understanding flatpak, this seems a confusing mess.

13

Yes, Flatpak maintains its own version of the KDE environment, irrespective of what is installed (or not) on the main system.
I cannot comment on the other points, sorry.

14

Okay, thanks. That’s sounding like flatpak has it’s own system to be maintained and at least with the KDE environment, those two things don’t substitute for the other, are not shared.

15

In a command prompt, if I do flatpak list, I see Mesa, gecko, mono, q4wine, but no wine. I’m thinking I need to install Wine in flatpak rather than in the through Myrlyn?
I’m still ambiguous of what deano_ferrari was agreed to.

16

You cannot mix wine from the openSUSE repos with q4wine from flatpak.

You need both packages either from the openSUSE repos OR from flatpak.

17

I downloaded Wine in flatpak, and same result. Exit -1. Running command from the log message:

> /usr/bin/env  WINE='/app/bin/wine'  WINEPREFIX='/home/kit/.wine'  WINESERVER='/app/bin/wineserver'  WINELOADER='/app/bin/wine'  WINEDEBUG='-all'  /bin/sh -c "cd '/home/kit' &&   '/app/bin/wine'   'wineconsole' --backend=user cmd 2>&1 "
/bin/sh: line 1: /app/bin/wine: No such file or directory

I do find a wine in

/var/lib/flatpak/runtime/com.fightcade.Fightcade.Wine/x86_64/stable/active/files/bin/
18

At the risk of annoying myself even further, and repeating myself.

You cannot just directly call /app/bin/foo if something is installed from flatpak.

Period.

It’s never going to work.

Flatpaks run in a containerized fashion.

You have to use flatpak run org.WineHQ.q4wine --command /app/bin/wine or something.

It will not generally work any other way, you have to call the flatpak binary, to do things with flatpaks.

2 Likes
19

Sorry.
I guess I don’t know what I’m supposed to do with that information. Maybe you’re saying I can’t test it that way in the terminal. q4wine did that exec string command. It gave an exit code of 256. Nothing listed in STDOUT and STDERR. So if I can’t execute that same command in the terminal, I don’t know the reason it doesn’t work. Nor do I know how to insert flatpak run into the exec string to test it.

20

He said exactly what he wrote.

Flatpak programs are not regular executables. Even it is different, you can think about a windows/MS-Dos program executed with Wine: you have to run wine and “tell” wine that runs the program, i.e.: wine myWinProgram

If you use a flatpak program (i.e. VLC, you need tell Flatpak that runs the program, i.e.: flatpak run vlc (in the special format of flatpak, i.e. flatpak run com.vlc.videolan…)

To run a Windows program with a wine flatpak, you need use the right command, some as flatpak run org.WineHQ.q4wine --command /app/bin/wine, you need query the right command.

But you only needs wine+q4wine from flatpak or wine+q4wine from Myrlyn. But Myrlyn search is not good. You need search for wine and surely you’ll need to search q4wine. Install both. Or both as flatpaks.