[Bug 40802] New: Loading Skyrim via Steam display the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

Bug ID: 40802
           Summary: Loading Skyrim via Steam display the title screen,
                    then exits to Steam window
           Product: Wine
           Version: 1.7.16
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 54733
  --> https://bugs.winehq.org/attachment.cgi?id=54733
Wine error log generated from Steam's failure to load Skyrim

Installed the Steam client (Windows version) from my Skyrim CD. Downloaded the
Skyrim package (no mods). Launching the game shows the title screen (no text)
and the app crashes (back to the Steam window) with the window that lets me
generate the backtrace log.

Slitaz release 5 / kernel update 3.2.71

Steam API v017
Steam package versions: 1465948400

4GB RAM / AMD E300 processor

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

david  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Loading Skyrim via Steam    |Loading Skyrim via Steam
                   |display the title screen,   |displays the title screen,
                   |then exits to Steam window  |then exits to Steam window

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from [e-mail] ---
You should really upgrade your wine version. All bugs should be opened against
development version of wine, so all the fixes will land in next stable version.

The other reason to upgrade is that your wine version is really outdated.
Latest currently relased is 1.9.12. You are at least 1 year behind in
development cycle. That's a lot code additions in wine source code.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

Qwerty Chouskie  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Qwerty Chouskie  ---
Your kernel is also really outdated...

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #3 from david  ---
This is ridiculous. I go through the time and stress of the net-install of
Debian (Jessie), only to find out the Wine version in their repos is even older
than the one in Slitaz (1.6.2). So what am I supposed to do - ignore the repos
and install the 1.9.*? I really liked Slitaz - mainly for its simplicity and
small size compared to bloated distros like Mint. Yet Qwerty is right - despite
all the updates their kernel begs updating. But the real selling point for my
switch to Debian was the level of community support.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

Rosanne DiMesio  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |normal

--- Comment #4 from Rosanne DiMesio  ---
(In reply to david from comment #3)
> So what am I supposed to do - ignore
> the repos and install the 1.9.*?

Yes. On Debian, you can use the WineHQ packages. https://wiki.winehq.org/Debian

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #5 from david  ---
Typical technician's syndrome. The last time I was here, I got all the way to
putting in the URL in the repos section of synaptic (graphical), & it claimed
the URL didn't exist. This time around I got this message:

The method driver /usr/lib/apt/methods/https could not be found.

So I installed that and this time everything went smoothly.

But now my major concern is Multiarch, since Steam uses 32-bit code (and I have
a 64-bit system). The reference page implied that since wine-builds does not at
present use source code, I wouldn't have worry about compilation - and
compilation is only mentioned in reference to Multiarch. Does 'add-architecture
i386' simply augment Wine's functionality - or is it part of Multiarch and more
involved?

After my last post, I thought I'd install the Debian version of Steam - until I
kept getting error messages because of useless drivers Valve included (e.g.
libgcc++, etc.). A web search showed dozens 'solutions' marked "SOLVED" on
message boards which indicated the best answer was to remove said files. Until
my browser stopped loading and not even apt-get worked in the terminal. So I
had reinstall everything -from scratch - the OS too.

So - thank you, Ms. R.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #6 from Rosanne DiMesio  ---
(In reply to david from comment #5)
> Does
> 'add-architecture i386' simply augment Wine's functionality - or is it part
> of Multiarch and more involved?

32 bit libraries are needed to run 32 bit apps in Wine. Enabling multiarch is
required for Wine to function properly, whether you build it yourself or use a
binary package.
> After my last post, I thought I'd install the Debian version of Steam -

The Linux version of Steam won't run Windows games and has nothing to do with
this bug.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #7 from david  ---
[1] I needed Wine for the CD - because the installer and the client are
Windows-based, of course.

[2] I mentioned the Debian version because I figured I would try it if I
couldn't get Wine working (and/or the Win version of Steam).

[3] Since I already have a Steam account, I would just need to get the client
working.

[4] As far as the 'Linux version of Steam', it depends on who you talk to.
Several people have claimed to have gotten Skyrim to run, although not
perfectly. It will still crash periodically.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #8 from david  ---
I think I'll hold off this whole thing until Debian fixes it.
> From the WineHQ forum here: viewtopic.php?f=8&t=25496

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #9 from david  ---
And -- thanks to all who responded.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #10 from Qwerty Chouskie  ---
(In reply to david from comment #3)
> This is ridiculous. I go through the time and stress of the net-install of
> Debian (Jessie), only to find out the Wine version in their repos is even
> older than the one in Slitaz (1.6.2). So what am I supposed to do - ignore
> the repos and install the 1.9.*? I really liked Slitaz - mainly for its
> simplicity and small size compared to bloated distros like Mint. Yet Qwerty
> is right - despite all the updates their kernel begs updating. But the real
> selling point for my switch to Debian was the level of community support.

If you want a system that is pretty up-to-date (except Wine packages in the
repo, just use the official Wine PPA), almost always just works, and is light
and simple, I would recommend Xubuntu.  http://xubuntu.org/

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

david  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #54733|0                           |1
        is obsolete|                            |

--- Comment #11 from david  ---
Created attachment 55060
  --> https://bugs.winehq.org/attachment.cgi?id=55060
Log generated during Steam/Skyrim installation/launching

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #12 from [e-mail] ---
(In reply to david from comment #5)
> Typical technician's syndrome. The last time I was here, I got all the way
> to putting in the URL in the repos section of synaptic (graphical), & it
> claimed the URL didn't exist. This time around I got this message:
>
> The method driver /usr/lib/apt/methods/https could not be found.
>
> So I installed that and this time everything went smoothly.
>
> But now my major concern is Multiarch, since Steam uses 32-bit code (and I
> have a 64-bit system). The reference page implied that since wine-builds
> does not at present use source code, I wouldn't have worry about compilation
> - and compilation is only mentioned in reference to Multiarch. Does
>
> 'add-architecture i386' simply augment Wine's functionality - or is it part
> of Multiarch and more involved?
>
> After my last post, I thought I'd install the Debian version of Steam -
> until I kept getting error messages because of useless drivers Valve
> included (e.g. libgcc++, etc.). A web search showed dozens 'solutions'
> marked "SOLVED" on message boards which indicated the best answer was to
> remove said files. Until my browser stopped loading and not even apt-get
> worked in the terminal. So I had reinstall everything -from scratch - the OS
> too.
>
> So - thank you, Ms. R.

Apologies for the offtopic but Antergos uses the Arch repos and they offer Wine
in multilib format: https://www.archlinux.org/packages/multilib/x86_64/wine/

This will a) allow you to run 32-bit and 64-bit applications without needing
separate Wine versions and b) is always up to date and hassle-free.

In any case, you are still using Wine 1.6.2 so it's up to you to decide if you
wish to switch to a distro that allows you to have easy access to a more
updated version of Wine.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEEDINFO

--- Comment #13 from Austin English  ---
(In reply to david from comment #11)
> Created attachment 55060 [details]
> Log generated during Steam/Skyrim installation/launching

Again, 1.6.2 is unsupported. Upgrade to a supported version and retest.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #14 from david  ---
I have installed the Debian 8 Jessie 64-bit OS. I followed the instructions at
https://wiki.winehq.org/Debian but for some reason I installed the latest Wine
package @ 1.7~. That was responsible for the backtrace log. Next I uninstalled
wine completely and installed the winehq-devel as suggested. No backtrace this
time, and Steam works ok. But Skyrim forces low-quality settings and is
extremely sluggish, and freezes when I try to exit.

AMD E-300 processor

4 GB RAM

ATI Video Card -- VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Wrestler [Radeon HD 6310]

Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)

I ran Skyrim on this system when it was pre-installed with Win8, and it ran
near flawless, even at higher settings (I didn't max too much, I didn't want to
stress the system). So I know the hardware is up to specs.

Thanks to all respondents for their tolerance and patience.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #15 from david  ---
I guess once the backtrace logs stopped coming, everyone lost interest. If
there's an error, the log should be auto-generated. 
The last time the app froze, Nothing responded - so I had to do a hard reboot.
But when I got to the desktop, none of my usb ports were functioning. I
followed a tip on another page... I powered down completely, unplugged
everything including the battery, and powered up after 5 minutes. Ports
restored. 
I'm tempted to uninstall Skyrim/Wine again - I can't risk bug-hunting until
something happens to make my system unbootable.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #16 from david  ---
Just updated Wine to the latest dev version - now returns 1.9.15.

Trying to run the Steam launcher generated a backtrace this time. Haven't tried
Skyrim yet.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #17 from david  ---
Created attachment 55202
  --> https://bugs.winehq.org/attachment.cgi?id=55202
backtrace.txt

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #18 from [e-mail] ---
(In reply to david from comment #17)
> Created attachment 55202 [details]
> backtrace.txt

This backtrace has nothing to do with skyrim. It's known issue with steam.

Does the game work or not? If yes then this bug report is a dupe/invalid.

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

--- Comment #19 from [e-mail] ---
(In reply to david from comment #16)
> Just updated Wine to the latest dev version - now returns 1.9.15.
>
> Trying to run the Steam launcher generated a backtrace this time. Haven't
> tried Skyrim yet.

Does skyrim work now or not?

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

https://bugs.winehq.org/show_bug.cgi?id=40802

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #20 from [e-mail] ---
Skyrim worked for me up through wine-2.16, and works through wine-2.19 staging
for me, except for with a USB controller (which has never worked).

[Bug 40802] Loading Skyrim via Steam displays the title screen, then exits to Steam window

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=40802

joaopa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #21 from joaopa  ---
Old wine version used.
Skyrim is reported working many times.
No news from the OP since 4 years.
Can an administrator close this bug as ABANDONED?