First Startup Wizard - Methinks it is Orko

[Connor84]

I had q4wine and wine installed in my Fedora 26 and they ran great. Recently I reinstalled and upgraded to F27. Now when I try to use q4wine it opens with a First Startup Wizard box. It did not have to do this before. I don't know what to enter for "Console application settings: Binary, (and) Arguments". I like q4wine because it allowed me to enter a virtual desktop and it automatically created desktop links for games which wine by itself does not always do.. (and I don't know how to myself)

[brezerk]

Hi @Connor84

q4wine requires one of following console terminals to be installed:

• xterm
• konsole (a part of KDE environemnt)

if you are using different console terminal -- let me know.

[Connor84]

After a little digging, my Fedora 27 uses gnome-terminal. Should I install xterm or konsole, just for q4wine? As I mentioned, using q4wine only a couple weeks ago in F26 worked fine. Maybe F26 had one of those 2 terminals? Or was there an update to q4wine (that changed the terminals it runs in) during this time?

[brezerk]

By looking into code i see no logic for gnome-terminal detection at the wizard stage.

If you wish to use it, you may wish to set this options:

• Binary: /usr/bin/gnome-terminal (Note: this path is just a guess, you can get fill path via which gnome-terminal command.)
• Arguments: -e

How to test:

1. Select any Icon in the Programs tab (winecfg for example)
2. Right click -> Options
3. Navigate to Advanced tab.
4. Select Run with output to console
5. Click Ok
6. Run Icon
7. q4wine should run selected wine program using gnome-terminal (you will see a lot of wine's stderr/stdout massages in it)

Let me know if you was able test gnome-terminal support so I can update auto detection logic to support it for you.

[Connor84]

Some strange things.

1 - I used your binary and argument. q4 was happy with that. I tried installing a game that I had previously working via F26 and q4wine. It installed. I ran the game (it started in full screen as normal). Now on the title screen when I scroll to the outer edge of the screen, it scrolls to the desktop. This is new.

2 - Then I tried regedit (which was working fine in F27 prior to installing q4wine, and just fine in F26 with q4wine). Whenever I scroll over a Wine window, the pointer disappears and I am not able to click on anything in the window. Only the top bar of the window is clickable (and shows the pointer). I tried uninstalling q4wine, but this issue persisted.

3 - Attempting to follow your instructions, if I right click in my menu on any item (including winecfg), there is only: Add to panel, Add to desktop, Add to favorites. No advanced tab.

Edit: Mybad. I rebooted my puter and issue 2 was solved. I thought that Linux was different than Windows and MacOSx, so that things would not go awry during the normal operation of the OS, requiring a reboot.

[tehnick]

Do you use XOrg or Wayland sessions of GNOME in F26 and in F27?

[Connor84]

I don't know what that means. I checked dfndragora and it seems that both XOrg and Wayland are installed. I don't know what these are and if one or both are running.

[brezerk]

Hi @Connor84

not sure about 1 and 2 issues -- this seems to be related to wine and F27 itself.
Are you able to reproduce this issues w/o q4wine installed and fresh wine prefix?

As for 3: this steps needs to be done via the q4wine gui:

1. Select any Icon in the Programs tab (winecfg for example)
2. Right click -> Options
   
3. Navigate to Advanced tab.
4. Select Run with output to console
5. Click Ok
   
6. Run Icon
7. q4wine should run selected wine program using gnome-terminal (you will see a lot of wine's stderr/stdout massages in it)
   

[Connor84]

I do not know how to get to the screen in your step 2. I tried launching the 13 items in my q4wine submenu and none of them show a screen like that one.

[Connor84]

I was installing an app via q4wine, and it opened up the gui. I was then able to follow your instructions. (I don't know why there would not be a q4wine gui option in the start menu.) Here is the output:

fixme:winediag:start_process Wine Staging 2.20 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.

[brezerk]

Thank you so much for testing and reporting.

Terminal detection logic has been updated to support gnome-terminal 427cec5

As for q4wine gui option: this seems to be strange for me too.
Can you confirm you have /usr/share/applications/q4wine.desktop file installed on your system?

[Connor84]

/usr/share/applications/q4wine.desktop is present

[brezerk]

Thanks for confirmation.

q4wine.desktop file is a standard for applications to integrate into a desktop environment. as long as it is present, your desktop environment should pick it up and show in the applications menu.

If you see no q4wine gui entity in the applications menu -- this is most likely to be a bug of your current desktop environment.