http://bugs.winehq.org/show_bug.cgi?id=58455
Bug ID: 58455
Summary: Word Pro loses path to a freshly opened file
Product: Wine
Version: 10.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
Distribution: ---
SmartSuite-N99.8.0208.0800
Fedora 42
wine-devel-10.11-1.1.x86_64
Also reproducible under
Fedora 41
wine-10.4-2.fc41.x86_64 (Staging from the Fedora repo)
wine-10.4-2.fc41.i686
[1] open an existing .lwp file in Word Pro
[2] make a change
[3] press the save icons of file→save
[4] you will be prompted for “Save As” instead of “Save”
This is because Word Pro lost the path to your file
[5] navigate back to your file and press “save” Okay the overwrite warning
[6] make another change to your file
[7] now press save. This time it will work.
AND! this is not an issue under
Fedroa 39
wine-9.1-1.fc39.i686 (staging from the Fedora repo)
This is a complete pain-in-the-neck.
Please fix.
--
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=53391
Bug ID: 53391
Summary: Unable to edit documents in Word Pro do to dictionary
pop up
Product: Wine-staging
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 72782
--> https://bugs.winehq.org/attachment.cgi?id=72782
User dictionary error
Fedora 36
Wine 7.12-1
Word Pro N99.8.0208.0800
I am unable to edit document is work pro due to a constant pop up "Cannot load
one or more user dictionaries" (see the attachment.)
Reverting to wine-7.2-1 solves the issue, but brings back the bug where
Approach crashes when printing to CUPS-PDF
--
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=42232
Bug ID: 42232
Summary: Sort version list by version number
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86
URL: https://appdb.winehq.org/objectManager.php?sClass=appl
ication&iId=13986
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cges30901(a)gmail.com
Distribution: ---
Versions of LINE (Powered by Naver) is not sorted correctly. Version 4.10.x.x
and 4.11.x.x is not at the bottom of the list. I guess this is because '1' in
10 is less than '3'?
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58483
Bug ID: 58483
Summary: Burnout Paradise has rendering issues
Product: Wine
Version: 10.1
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: 96fb128efdbf8d92f6b4d63a7db0346659b08969
Distribution: ---
Created attachment 78933
--> http://bugs.winehq.org/attachment.cgi?id=78933
examples
Some scenes are black rendered.
--
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=52092
Bug ID: 52092
Summary: game pass
Product: Wine
Version: 6.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: master.zion(a)gmail.com
Distribution: ---
Hi everyone...
it seems it is not possible to install the xbox application for PC using wine.
It would be useful to play Windows games from xbox game pass, and it will be
very useful on Steam deck.
it fails during the installation startup.
------
Unhandled Exception: 0024:fixme:ntdll:EtwEventRegister
({8e9f5090-2d75-4d03-8a81-e5afbf85daf1}, 05E202EE, 00000000, 01EA96F4) stub.
Unhandled Exception: System.IO.FileNotFoundException: Could not load file or
assembly 'Windows.Foundation.UniversalApiContract, Version=7.0.0.0,
Culture=neutral, PublicKeyToken=null, ContentType=WindowsRunt
ime' or one of its dependencies. Module not found.
at XboxInstaller.App..ctor()
at XboxInstaller.App.Main()
------
https://www.xbox.com/en-IN/apps/xbox-app-for-pc
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58415
Bug ID: 58415
Summary: Wine msiexec behaviour deviates from MS msiexec for
tables missing from .msi
Product: Wine
Version: 10.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: depaoli.renzo(a)gmail.com
Distribution: ---
While investigating a problematic .msi file, I noticed the following:
The .msi file in its InstallExecuteSequence calls functions that depend on
tables in the msi. However these tables do not exit.
Examples found:
"LaunchConditions", but no "LaunchCondition Table"
"IsolateComponents", but no "IsolatedComponent Table"
"PublishComponents/UnpublishComponents", but no "PublishComponent Table"
"RegisterMIMEInfo/UnregisterMIMEInfo", but no "MIME table"
"RegisterTypeLibraries/UnregisterTypeLibraries", but no "TypeLib table"
"RegisterComPlus/UnregisterComPlus", but no "Complus table"
When MS msiexec processes the .msi, it reports "Return value 0" in these cases.
However when Wine msiexec does the same, it reports "Return value 1" instead.
When modifying the .msi with the Orca MSI editor adding the missing tables
(left empty), then MS msiexec reports "Return value 1", and Wine msiexec does
the same.
So there is a mismatch between the two implementations; I would conclude that
Wine msiexec is missing a check for missing tables.
Whether there are problems resulting from this difference in behaviour I cannot
say, but it is at least not making investigations of .msi-issues any easier.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58326
Bug ID: 58326
Summary: SetupDiGetClassDevs does not enumerate USB devices
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: setupapi
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)3v1n0.net
Distribution: ---
Created attachment 78694
--> http://bugs.winehq.org/attachment.cgi?id=78694
Example device enumerator
In order to enumerate the USB devices in the system, a window application is
expected
(https://github.com/microsoft/Windows-driver-samples/blob/main/usb/usbview/e…)
to use SetupDiGetClassDevs with the `GUID_DEVINTERFACE_USB_DEVICE` GUID,
however this returns nothing in WINE.
Running a simpler example (attached) of the enumerator that extends to all the
device types, I get in fact:
```
Device info is 0x7ffffe8d4760
Device info Date is 1 {4D36E96E-E325-11CE-BFC1-08002BE10318}
Device desc name is Generic Non-PnP Monitor
Device driver name is {4D36E96E-E325-11CE-BFC1-08002BE10318}\0000
Failed at 186
Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}
Device desc name is Wine HID device
Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0003
Failed at 186
Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}
Device desc name is Wine HID device
Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0002
Failed at 186
Device info Date is 1 {4D36E968-E325-11CE-BFC1-08002BE10318}
Device desc name is Wine Adapter
Device driver name is {4D36E968-E325-11CE-BFC1-08002BE10318}\0000
Failed at 186
Device info Date is 1 {4D36E97D-E325-11CE-BFC1-08002BE10318}
Device desc name is Wine HID bus driver
Device driver name is {4D36E97D-E325-11CE-BFC1-08002BE10318}\0000
Failed at 186
Device info Date is 1 {4D36E97D-E325-11CE-BFC1-08002BE10318}
Device desc name is Wine USB bus driver
Device driver name is {4D36E97D-E325-11CE-BFC1-08002BE10318}\0001
Failed at 186
Device info Date is 1 {00000000-0000-0000-0000-000000000000}
Failed at 159
Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}
Device desc name is Wine HID compatible device
Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0000
Failed at 186
Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}
Device desc name is Wine HID compatible device
Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0001
Failed at 186
Device info Date is 0 {00000000-0000-0000-0000-000000000000}
```
While under a windows VM the same code also returns (for example):
Device info Date is 1 {CA3E7AB9-B4C3-4AE6-8251-579EF933890F}
Device desc name is
USB Video Device
Device driver name is
{ca3e7ab9-b4c3-4ae6-8251-579ef933890f}\0001
As per this it's not possible to find out the device ID that it could be used
via `WinUsb_Initialize(deviceHandle, &winusbHandle)` (even though this doesn't
seem to work even passing an hardcoded path).
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58532
Bug ID: 58532
Summary: error in solidworks 2023
Product: Wine
Version: 10.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: grandrodri3(a)gmail.com
Distribution: ---
Created attachment 79015
--> http://bugs.winehq.org/attachment.cgi?id=79015
edrawings first error
Hey, hi, how are you? Here's an error from an old friend, SolidWorks. I tried
version 2023, and Edrawings gives two programming errors. I'm uploading them
now to see if anything can be done about them. The viewer works without any
problems.
This was initially done without IE8. Let's see if it works without uninstalling
the one that comes with Wine.
Oh, the DLLs that were installed:
dotnet48 vcrun2019 d3dcompiler_47 corefonts msxml6
Visual C++ 2010 and 2012 were installed, the ones that came with SolidWorks
2023, and they installed without any problems.
Could you please check?
Best regards.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58498
Bug ID: 58498
Summary: OSS driver is triggering Rocket League crash
Product: Wine
Version: 10.10
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineoss.drv
Assignee: wine-bugs(a)winehq.org
Reporter: sean-freebsd(a)farley.org
This is an odd issue. Rocket League currently has an issue that causes it to
crash with a very brief burst of static related to the sound device used. One
reported workaround for Windows is to switch from headphones to speakers in
settings:
https://www.reddit.com/r/RocketLeague/comments/1lflw0s/were_aware_of_a_seas…
However, I already have it set to speakers in the game and stereo in winecfg.
I tried most configuration of OSS on my system without luck. The only thing
that made it run was to change dev.pcm.4.rec.vchanformat from s16le:2.0 to
s32le:2.0, however, this causes this game (not others) to produce very
distorted sounds.
OTOH, I can run the game using ALSA, so that helps push the theory that the OSS
driver is reporting something odd to the game or looks like headphones to it.
Unfortunately, I have no idea.
System:
- FreeBSD 14.3-STABLE
- Wine 10.10
- Nvidia 4070
- Both ALC4080 and Creative AE-5 Plus
wineoss.drv trace of the primary playback device:
01fc:trace:oss:oss_create_stream OSS audioinfo:
01fc:trace:oss:oss_create_stream devnode: /dev/dsp4
01fc:trace:oss:oss_create_stream name: dsp4.virtual_play.0
01fc:trace:oss:oss_create_stream busy: 2
01fc:trace:oss:oss_create_stream caps: 63200
01fc:trace:oss:oss_create_stream iformats: 0
01fc:trace:oss:oss_create_stream oformats: 10
01fc:trace:oss:oss_create_stream enabled: 1
01fc:trace:oss:oss_create_stream min_rate: 1
01fc:trace:oss:oss_create_stream max_rate: 2016000
01fc:trace:oss:oss_create_stream min_channels: 2
01fc:trace:oss:oss_create_stream max_channels: 2
01fc:trace:oss:setup_oss_device returning: 00000000
020c:trace:oss:oss_write_data New buffer size (8192) is larger than old buffer
size (0)
winealsa.drv trace of the primary playback device:
022c:trace:alsa:map_channels Mapping mmdevapi channel 0 (0x1) to ALSA channel 0
022c:trace:alsa:map_channels Mapping mmdevapi channel 1 (0x2) to ALSA channel 1
022c:trace:alsa:map_channels need_remapping: 0, alsa_channels: 2
022c:trace:alsa:alsa_create_stream ALSA period: 480 frames
022c:trace:alsa:alsa_create_stream ALSA buffer: 1920 frames
022c:trace:alsa:alsa_create_stream MMDevice period: 480 frames
022c:trace:alsa:alsa_create_stream MMDevice buffer: 2048 frames
sndctl information about device:
pcm4: <Creative CA0132 (Rear Analog)> on hdaa1 (play/rec)
name = pcm4
desc = Creative CA0132 (Rear Analog)
status = on hdaa1
devnode = dsp4
from_user = 0
unit = 4
caps = INPUT,MMAP,OUTPUT,REALTIME,TRIGGER
bitperfect = 0
autoconv = 1
realtime = 0
play.format = s16le:2.0
play.rate = 48000
play.vchans = 1
play.min_rate = 1
play.max_rate = 2016000
play.min_chans = 2
play.max_chans = 2
play.formats = s16le,s32le
rec.rate = 48000
rec.format = s16le:2.0
rec.vchans = 1
rec.min_rate = 1
rec.max_rate = 2016000
rec.min_chans = 2
rec.max_chans = 2
rec.formats = s16le,s32le
--
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.