• melroy@kbin.melroy.org
    link
    fedilink
    arrow-up
    23
    ·
    11 months ago

    /me stil trying to get MS Office working under Wine… But this Wine under Wayland is great news! I’m the developer of WineGUI so I’m in!

    • leopold@lemmy.kde.social
      link
      fedilink
      English
      arrow-up
      9
      ·
      11 months ago

      I’m assuming you probably already know since you’re making WineGUI, but older versions of Office (particularly Office 2010 32bit) are pretty simple to get working. Just need to install some dependencies with Winetricks.

  • Chewy
    link
    fedilink
    arrow-up
    11
    ·
    11 months ago

    I’m impressed how well wine-wayland already works. Some games still have issues with mouse locking, at least Overwatch doesn’t register the at all. But as they said, bugs will be fixed over time.

    • Rustmilian@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      11 months ago

      I have issues with game resolution, when using Wine-Wayland the only resolution available is the one already set for my display, which renders FSR completely useless. As well as this little cursor render bug that sticks a frozen windows cursor on the screen, though I’ve been able to work around this.

  • Pantherina@feddit.de
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    11 months ago

    Are Wine apps ran isolated? Because we basically have no viruses on Linux, but I imagine running random of course legally obtained games may be very risky

    • Chewy
      link
      fedilink
      arrow-up
      5
      ·
      11 months ago

      No, the Linux filesystem is usually mounted as Z: in wine. Sandboxing through e.g. flatpak/bubblewrap with permissions set to only allow access to ~/Games should protect from many viruses.

          • Pantherina@feddit.de
            link
            fedilink
            arrow-up
            2
            ·
            11 months ago

            Wine does not sandbox in any way at all. When run under Wine, a Windows app can do anything your user can. Wine does not (and cannot) stop a Windows app directly making native syscalls, messing with your files, altering your startup scripts, or doing other nasty things.

            You need to use AppArmor, SELinux or some type of virtual machine if you want to properly sandbox Windows apps.

            Note that the winetricks sandbox verb merely removes the desktop integration and Z: drive symlinks and is not a true sandbox. It protects against errors rather than malice. It’s useful for, e.g., keeping games from saving their settings in random subdirectories of your home directory.

            So yes, Bottles Flatpak for the win!

  • iopq@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    11 months ago

    Maybe once it’s ready I’ll get my distro to package the staging patches version. I have no way of testing it because my game needs staging patches

    • Laser@feddit.de
      link
      fedilink
      arrow-up
      3
      ·
      11 months ago

      I’m on 9.0 staging and can use wine with Wayland, but not everything works, window bars etc look somewhat off and some games don’t start at all, like Stardew Valley. Other games I tried failed to hide the cursor. Others worked just fine.

      • Emanuel@lemmy.eco.br
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        How do you make wine run without Xwayland? Just wondering if you could point me to some resource

        • Laser@feddit.de
          link
          fedilink
          arrow-up
          5
          ·
          11 months ago

          It’s in the release notes, you add a Wayland driver to your prefix via registry entry and then unset DISPLAY before starting wine.

          https://gitlab.winehq.org/wine/wine/-/releases/wine-9.0

          The Wayland driver is not yet enabled by default. It can be enabled through the HKCU\Software\Wine\Drivers registry key by running:

          wine reg.exe add HKCU\Software\Wine\Drivers /v Graphics /d x11,wayland

          and then making sure that the DISPLAY environment variable is unset.

          Note that the registry entry is per prefix.

          • Emanuel@lemmy.eco.br
            link
            fedilink
            arrow-up
            1
            ·
            11 months ago

            Thank you, last I checked on the progress on the wayland driver was around this time last year