https://bugs.winehq.org/show_bug.cgi?id=53597
Bug ID: 53597
Summary: This has more or less disabled my Update Manager
Product: Wine
Version: 7.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lilleyen(a)gmail.com
Distribution: ---
Created attachment 72987
--> https://bugs.winehq.org/attachment.cgi?id=72987
has diabled my Update Manager
After trying to install Wine vers.7 into my Linux Mint V21, I keep getting this
error message from my update manager.
I have no idea how to fix this.
The error message is copied into the attachment box below
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53563
Bug ID: 53563
Summary: SWAT 4: frequent crashes with "page fault on write
access" error
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matheus.venturini(a)acad.ufsm.br
Distribution: ---
Created attachment 72930
--> https://bugs.winehq.org/attachment.cgi?id=72930
backtrace generated by Wine
SWAT 4 crashes frequently at seemingly random points of the game. This happens
both when using 64-bit and 32-bit prefixes. I've had three crashes that made
the game quit suddenly and three which generated a backtrace, which I've added
as attachment, all three with the same "page fault on write access on 32-bit
code" error. Since the game saves progress when quitting to the desktop, this
can lead to loss of data.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=51882
Bug ID: 51882
Summary: Application using third party DLL can't use COM object
(class not registered)
Product: Wine
Version: 6.18
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Reported in the forums: https://forum.winehq.org/viewtopic.php?f=8&t=32385
--
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.
https://bugs.winehq.org/show_bug.cgi?id=39627
Bug ID: 39627
Summary: BreezeBrowser Pro 1.x crashes on start
Product: Wine
Version: 1.7.34
Hardware: x86
URL: http://www.breezesys.com/downloads/bbpro1987.exe
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com
Regression SHA1: ca51e113e4820f8b11016c13732b1a971d2b0054
Distribution: ---
The application crashes immediately after starting (no backtrace is generated
for me):
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:ntdll:server_ioctl_file Unsupported ioctl 900a8 (device=9 access=0
func=2a method=0)
fixme:ntdll:server_ioctl_file Unsupported ioctl 900a8 (device=9 access=0
func=2a method=0)
wine: Unhandled exception 0x40000015 in thread 9 at address 0x80d930 (thread
0009), starting debugger...
If you manually create an empty 'dbglogs' directory under ~/Documents, then the
application starts properly.It seems the application fails to create that
directory for some reason.
Regression introduced by
commit ca51e113e4820f8b11016c13732b1a971d2b0054
Author: Erich E. Hoover <erich.e.hoover(a)gmail.com>
Date: Tue Aug 19 20:31:00 2014 -0600
ntdll: Unify retrieving the attributes of a file.
The commit can't be reverted on git (Wine build failure), however the
application starts properly with the previous commit (and dbglogs directory is
created).
Still present in wine-1.7.55-73-g39f2ed3.
bbpro1987.exe
sha1: ead99cf82bc8eeac4413ed4939891bbe57251058
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53414
Bug ID: 53414
Summary: Wine prefixes should have packages
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: abacadacaba(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ---
This should have been done from day 1.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=47618
Bug ID: 47618
Summary: Required gstreamer plugins not installed by Debian
packages
Product: Packaging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: jre.winesim(a)gmail.com
CC: dimesio(a)earthlink.net, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Hi,
from https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1817244 and followup
reading at winehq I learned that several gstreamer plugins are required for
some media, but the Debian packages don't install them.
In this specific case I couldn't reproduce the issue as long as
libmpg123-0:i386 was installed. But I assume current Wine still generally
needs them!? Please comment.
Unless you have some other input, I'm going to fix this in the debian.org
packages, and suggest you do something similar in the winehq -i386 and -amd64
packages:
Recommends:
gstreamer1.0-libav,
gstreamer1.0-plugins-good,
gstreamer1.0-plugins-ugly,
This works on Debian unstable.
gstreamer1.0-plugins-bad still has non multi-arch'd dependencies. I'll try to
get those fixed.
I assume some other distros don't support multi-arch for the previous 3
packages, so you might have to add this conditionally.
Also some distros might still use gstreamer 0.10.
Greets!
jre
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53378
Bug ID: 53378
Summary: File Open dialogs shows non-Latin names as junk
Product: Wine
Version: 7.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: abacadacaba(a)gmail.com
Distribution: ---
Dialog shows correct number of files.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=43193
Bug ID: 43193
Summary: MinGW-w64 GUI installer fails 66 per cent through its
file-installation page.
Product: Wine-staging
Version: 2.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: irwin(a)beluga.phys.uvic.ca
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
My platform is Debian Jessie, and I am using the WineHQ repository for that
distro following the advice at <https://wine-staging.com/installation.html>.
I installed the latest version (2.10) of winehq-staging and set the environment
variables
export WINEVERSION=2.10_jessie_wine_staging
export WINEPREFIX=/home/wine/wine_staging/.wine-$WINEVERSION
export WINEDEBUG='fixme-all'
and ran
winecfg
taking defaults for everything. Then
wine@raven> wine --version
wine-2.10 (Staging)
wineserver -p
nice -19 wine msys2-x86_64-20161025.exe
Welcome screen, set prefix (added date string to default location),
start menu shortcuts left as they were, then install page went
to the 66 per cent level and then generated
a Program Error GUI box with the message
The program bash.exe has encountered a serious error and needs to close. We
are sorry for the inconvenience.
Program error details page on GUI was empty.
stderr (or stdout) had the following messages on the konsole
instance I was running:
err:ole:CoCreateInstanceEx apartment not initialised
err:ole:CoCreateInstanceEx apartment not initialised
err:ole:CoCreateInstanceEx apartment not initialised
wine: Unhandled page fault on read access to 0x00000020 at address 0x7bc4b478
(thread 0045), starting debugger...
The installer GUI details showed the install failed (at the ~66 per cent mark)
while installing nansi.sys.
This is definitely a wine-staging bug because the equivalent experiment
with vanilla wine-2.10 (obtained by purging winehq-staging and installing
winehq-devel) had no troubles with that install page of the GUI (although the
above "apartment" warnings were produced), but failed in other ways on the
final page of that GUI.
Note it is likely this current wine-staging bug with the initial file
installation has been introduced in the past year since
<https://github.com/TeaCI/tea-ci/wiki/Msys2-on-Wine> implies MSYS2 works on
Wine-staging, and that page was last updated in July last year.
However, introduction of this wine-staging bug is not extremely recent because
I replicated this bug also for wine-staging 2.4 (the earliest version [released
March 2017] currently available for the winehq Debian Jessie repository.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53527
Bug ID: 53527
Summary: msctf:inputprocessor fails in the Japanese, Korean and
Chinese locales on Windows 10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: msctf
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
msctf:inputprocessor fails in the Japanese, Korean and Chinese locales on
Windows 10. The failures are the same in each case but are repeated a variable
number of times.
For instance Korean is the most stable with a systematic set of 6 failures:
inputprocessor.c:840: Got OnActivated: {clsid
{a028ae76-01b1-46c2-99c4-acd9858ae02f}, guidProfile
{b5fe1f02-d5f2-4445-9c03-c568f23c99a1}, activated 1}
inputprocessor.c:275: Test failed: Unexpected TextStoreACP_RequestLock sink
inputprocessor.c:296: Test failed: Unexpected TextStoreACP_GetSelection sink
inputprocessor.c:275: Test failed: Unexpected TextStoreACP_RequestLock sink
inputprocessor.c:275: Test failed: Unexpected TextStoreACP_RequestLock sink
inputprocessor.c:296: Test failed: Unexpected TextStoreACP_GetSelection sink
inputprocessor.c:275: Test failed: Unexpected TextStoreACP_RequestLock sink
inputprocessor.c:750: Got OnActivated: {dwProfileType 00000001, langid
00000412, clsid {a028ae76-01b1-46c2-99c4-acd9858ae02f}, catid
{34745c63-b2f0-4784-8b67-5e12c8701a31}, guidProfile
{b5fe1f02-d5f2-4445-9c03-c568f23c99a1}, 0000000000000000, dwFlags 00000003}
Japanese has between 9 and 24 of these failures, while Chinese has between 12
and 21.
https://test.winehq.org/data/patterns.html#msctf:inputprocessor
Also note that for all three locales these failures started on 2022-06-10
whereas these test configurations have not been changed since 2022-05-11 and
the test has not been modified since 2022-03-01. So it seems likely that there
is interference from another test.
--
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.