[Bug 49875] New: after OS updates to Fedora 32, wine will not start

List overview All Threads

newer

older

[Bug 38859] New: CMake hangs when...

[Bug 49958] New:...

WineHQ Bugzilla

21 Sep 2020 21 Sep '20

1:42 a.m.

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

Bug ID: 49875 Summary: after OS updates to Fedora 32, wine will not start Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: endzone102@gmail.com Distribution: ---

Created attachment 68219 --> https://bugs.winehq.org/attachment.cgi?id=68219 wine startup failure

After updating Fedora 32, wine has stopped working entirely.

I uninstalled wine and reinstalled it fresh, and it's just not getting started. It complains that it can't open a window!

Output attached

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

Show replies by date

WineHQ Bugzilla

21 Sep 21 Sep

2:28 a.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

joaopa jeremielapuree@yahoo.fr changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr

--- Comment #1 from joaopa jeremielapuree@yahoo.fr --- Sometimes, I receive these messages too. Run again winecfg will do the trick.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

2:33 a.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

--- Comment #2 from Greg G endzone102@gmail.com --- Sadly, I'm getting this every time. I ran winecfg three times in a row, and got these same messages every time.

FWIW, I'm running the Cinnamon desktop. Something in the update must be clashing with something in Wine. IDK.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

1:17 p.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

--- Comment #3 from Greg G endzone102@gmail.com --- There were a bunch of new patches last night, including an upgrade to Wine 5.17.1. It didn't fix the problem, but the error log looks a bit more robust, with several new error messages showing up.

I removed .wine and ran winecfg and captured the output.

I have attached that file here.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

1:17 p.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

--- Comment #4 from Greg G endzone102@gmail.com --- Created attachment 68222 --> https://bugs.winehq.org/attachment.cgi?id=68222 wine 5.17.1 startup failure

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

24 Sep 24 Sep

5:02 a.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

Greg G endzone102@yahoo.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |endzone102@yahoo.com

--- Comment #5 from Greg G endzone102@yahoo.com ---

Something in one of these made Wine happy again.

catatonit-0.1.5-3.fc32.x86_64 conmon-2:2.0.21-2.fc32.x86_64 firefox-81.0-3.fc32.x86_64 gucharmap-13.0.3-1.fc32.x86_64 gucharmap-libs-13.0.3-1.fc32.x86_64 libproxy-0.4.15-18.fc32.i686 libproxy-0.4.15-18.fc32.x86_64 libproxy-mozjs-0.4.15-18.fc32.x86_64 libsmbclient-2:4.12.7-0.fc32.x86_64 libwbclient-2:4.12.7-0.fc32.x86_64 samba-client-2:4.12.7-0.fc32.x86_64 samba-client-libs-2:4.12.7-0.fc32.x86_64 samba-common-2:4.12.7-0.fc32.noarch samba-common-libs-2:4.12.7-0.fc32.x86_64 samba-common-tools-2:4.12.7-0.fc32.x86_64 samba-libs-2:4.12.7-0.fc32.x86_64 samba-winbind-2:4.12.7-0.fc32.x86_64 samba-winbind-clients-2:4.12.7-0.fc32.x86_64 samba-winbind-modules-2:4.12.7-0.fc32.x86_64 systemd-245.8-2.fc32.x86_64 systemd-container-245.8-2.fc32.x86_64 systemd-libs-245.8-2.fc32.i686 systemd-libs-245.8-2.fc32.x86_64 systemd-pam-245.8-2.fc32.x86_64 systemd-rpm-macros-245.8-2.fc32.noarch systemd-udev-245.8-2.fc32.x86_64 zeromq-4.3.3-1.fc32.x86_64

I now only get the following error:

$ winecfg 002c:fixme:winediag:LdrInitializeThunk wine-staging 5.17 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0050:err:ole:start_rpcss Failed to start RpcSs service

and winecfg starts up.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

5:05 a.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

--- Comment #6 from joaopa jeremielapuree@yahoo.fr --- So, if wine is working after updating your system, the bug was not in wine. You can close your own bug with INVALID status.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

5:15 a.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

--- Comment #7 from Greg G endzone102@yahoo.com ---

Actually, I'm still having a problem with wine. It's not running any exe files, although the internal wincfg and wordpad are working. I tried both of these, and got the same results.

WINEARCH=win64 WINEPREFIX=~/.wine64 wine ./foobar2000_v1.6.exe WINEARCH=win32 WINEPREFIX=~/.wine32 wine ./foobar2000_v1.6.exe

wine: created the configuration directory '/home/Greg/.wine32' 002c:fixme:winediag:LdrInitializeThunk wine-staging 5.17 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0048:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 0048:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 0048:err:ole:apartment_get_local_server_stream Failed: 0x80004002 0050:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 0050:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 0050:err:ole:apartment_get_local_server_stream Failed: 0x80004002 0050:err:ole:start_rpcss Failed to open RpcSs service 0040:fixme:file:NtLockFile I/O completion on lock not implemented yet 0040:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0040:err:mscoree:LoadLibraryShim error reading registry key for installroot 0040:err:mscoree:LoadLibraryShim error reading registry key for installroot 0040:err:mscoree:LoadLibraryShim error reading registry key for installroot 0040:err:mscoree:LoadLibraryShim error reading registry key for installroot 0040:err:mscoree:LoadLibraryShim error reading registry key for installroot 0040:err:mscoree:LoadLibraryShim error reading registry key for installroot 0040:err:mscoree:LoadLibraryShim error reading registry key for installroot 0040:err:mscoree:LoadLibraryShim error reading registry key for installroot 0040:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1) 0040:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1) 006c:fixme:file:NtLockFile I/O completion on lock not implemented yet 006c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 006c:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1) 006c:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1) 0040:fixme:dwmapi:DwmIsCompositionEnabled 0F9FBD34 0074:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0xb52f617, context 0xfcad8e0, init_notify 0, handle 0x106bfccc): stub 00b8:err:service:process_send_command receiving command result timed out 002c:err:setupapi:SetupDiInstallDevice Failed to start service L"winebus" for device L"ROOT\WINE\WINEBUS", error 1053. wine: configuration in L"/home/Greg/.wine32" has been updated. 0024:err:process:exec_process L"Z:\home\Greg\Downloads\foobar2000_v1.6.exe" not supported on this system

I've tried a few other exe's, and they all give the same.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

5:48 a.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

--- Comment #8 from Dmitry Timoshkov dmitry@baikal.ru --- (In reply to Greg G from comment #7)

...

0024:err:process:exec_process L"Z:\home\Greg\Downloads\foobar2000_v1.6.exe" not supported on this system

What does 'file' report about that .exe?

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

3 Oct 3 Oct

12:50 a.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

--- Comment #9 from Greg G endzone102@yahoo.com ---

As far as I can tell, there was some wonky issue with the system updates that wasn't playing well with wine. I'm now able to launch most programs. There are still a few, like the Winamp installer (winamp58_3660_beta_full_en-us.exe) that are breaking, but it likely unrelated to this issue.

I appreciate the help.

I don't seem to be able to change the status. I guess either INVALID or NOTOURBUG would be appropriate.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

5:16 a.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

Robert Wilhelm sloper42@yahoo.com changed:

--- Comment #10 from Robert Wilhelm sloper42@yahoo.com --- Nice to read that wine is working again for you. Setting status to resolved invalid.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

12 Feb 12 Feb

10:14 a.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

--- Comment #11 from Austin English austinenglish@gmail.com --- Closing.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

10:14 a.m.

New subject: [Bug 49875] after OS updates to Fedora 32, wine will not start

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

Austin English austinenglish@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED

--- Comment #12 from Austin English austinenglish@gmail.com --- Closing.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1429

Age (days ago)

1573

Last active (days ago)

wine-bugs@winehq.org

12 comments

1 participants

tags (0)

participants (1)

WineHQ Bugzilla