http://bugs.winehq.org/show_bug.cgi?id=22904
Summary: Register URL protocol handlers under Linux
Product: Wine
Version: unspecified
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kempe.marcus(a)gmail.com
winemenubuilder is able to automatically register file type associations and
build menus under Linux, when triggered by an application under wine.
It would be great if the same thing were true for protocol handlers, so that
these would become registered in much the same way as when using gconftool in
gnome:
gconftool -s /desktop/gnome/url-handlers/spotify/command 'wine
c:\\spotify\\spotify.exe %s' --type String
gconftool-2 -s /desktop/gnome/url-handlers/spotify/enabled --type Boolean true
Would this be possible, hard, or maybe not a good idea?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=16214
Summary: Copy command does not work as expected
Product: Wine
Version: 1.0.1
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scott(a)open-vote.org
>From Launchpad: https://bugs.edge.launchpad.net/ubuntu/+source/wine/+bug/272921
In Windows, the COPY command run in a command prompt allows users to
concatenate files by using a plus ("+") operator, for example:
copy file1+file2 outfile
In wine's cmd.exe, it seems to read file1+file2 as a single path and therefore
outputs a "Path Not Found". Also, it does not recognize the "con" keyword used
to represent stdout/stdin. Therefore another method of concatenating files:
copy file1 outfile
copy file2 con >> outfile
does not work either.
My Ubuntu version is 8.04, AMD64 architecture, though I have seen the same
issue on the x86 version as well.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=20474
Summary: Wine can't be built with GCC in C99 mode
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build-env
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: yann(a)droneaud.fr
For multiple reason, wine can't be built by GCC in C99 mode ( --std=c99 ).
In particular, wine rely on GCC behavor regarding to extern inline.
It produces errors regarding asm construct conflicting with extern
inline symbols.
It produces errors with multiple defination of inline function in object files.
According to this, it seems that wine is not compatible with C99, but rely a
lot on GCC specific behavor.
See also bug #20306
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=53216
Bug ID: 53216
Summary: d3d11:d3d11 - test_depth_bias() fails in the TestBot
VMs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs:
d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected
4.99999994e-003.
d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected
4.99999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected
7.49999994e-003.
d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected
7.49999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected
1.24999999e-002.
d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected
1.24999999e-002.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected
6.42500000e-001.
d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected
6.42500000e-001.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected
2.50999994e-003.
d3d11.c:27965: Test marked todo: Got 0xffffff00, expected 0x00ffffff at (0, 0,
0), sub-resource 0.
d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected
0x147ae (4.99999553e-003).
d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected
0x147ae (4.99999553e-003).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected
0x1eb85 (7.49999329e-003).
d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected
0x1eb85 (7.49999329e-003).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected
0x33333 (1.24999888e-002).
d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected
0x33333 (1.24999888e-002).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected
0xa47ae1 (6.42500022e-001).
d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected
0xa47ae1 (6.42500022e-001).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected
0x85293 (3.25099845e-002).
d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290
(1.00099184e-002).
d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290
(1.00099184e-002).
d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334
(1.25123980e-002).
d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334
(1.25123980e-002).
d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b
(1.75020981e-002).
d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b
(1.75020981e-002).
d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a
(6.42496376e-001).
d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a
(6.42496376e-001).
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures:
* Don't happen on Debian 11 + Intel / KDE
* Happen on Debian 11 + QXL + single-monitor
* Happen on Debian 11 + QXL + multi-monitor
* Don't happen on Debian Testing + QXL + multi-monitor
So they are probably caused by some bug in the Debian 11 QXL support.
Note that despite being systematic these failures could cause false positives
due to the test multi-threading (see bug 53212).
--
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=48247
Bug ID: 48247
Summary: Darksiders 2 (GOG) crashes after intro
Product: Wine-staging
Version: 4.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fzielcke(a)z-51.de
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 65912
--> https://bugs.winehq.org/attachment.cgi?id=65912
log + crash dump with wine-4.20 (staging)
Darksiders 2 directly crashes after the intro.
This is on Debian unstable with the official winehq-staging 4.20 packages for
bullseye
--
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=54642
Bug ID: 54642
Summary: Page fault on read access to 0x0000
Product: Wine-staging
Version: 8.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: santafejayyt(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 74172
--> https://bugs.winehq.org/attachment.cgi?id=74172
Wine debugger backtrace on game start
I'm attempting to run Konami's E-Amusement Cloud Sound Voltex Exceed Gear game,
and the launcher and its components work fine, however when attempting to
launch the game, the window opens, but the game does not start, and stays on a
black screen. I have installed the required dependencies for the game via
winetricks (DXVK / D3DX9, FAudio, & XACT).
--
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=55086
Bug ID: 55086
Summary: Dotnet 7: System.Net.WebSockets.WebSocketException
(0x80004005) - SSL cannot be established
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: reiichi001(a)gmail.com
Distribution: ---
Created attachment 74637
--> https://bugs.winehq.org/attachment.cgi?id=74637
Error message from POC, which matches error from game modding project
As part of a game modding project, I maintain a plugin that makes use of
Discord.Net to relay game messages to Discord.
In recent versions of Wine with .Net 7 for Windows installed (as required by
the modding project, as it uses Windows .Net 7), Discord.Net will fail to
connect. Previously, this was due to WebSocket mishandling, which looks to have
been fixed in Wine 7.18.
When trying to connect to Discord's gateway in Wine 8.10 (current staging), an
SSL exception occurs and the connection fails. Please see attached logs.
I've made a quick POC with minimal functionality that can be used for
testing/code review. It will run fine on Windows and on native .Net 7
installations, but not in Wine. On discord, the bot will accept a single text
command, xl!ping and will respond with "pong" in an embed if working. In Wine,
it never connects as noted above.
https://github.com/reiichi001/DiscordNetWinePOC
--
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=55070
Bug ID: 55070
Summary: winemenubuilder adds incorrect prefix on 32bit only
Wine
Product: Wine
Version: 8.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dofficialgman(a)gmail.com
Distribution: ---
On 32bit (x86 only) wine, the Exec= line automatically created in an
application's .desktop file is incorrect and can not be launched.
eg: /home/gman/.local/share/applications/wine/Programs/7-Zip/7-Zip\ File\
Manager.desktop
```
[Desktop Entry]
Name=7-Zip File Manager
Exec=env WINEPREFIX="/home/gman/.wine/dosdevices/f:/home/gman/.wine" wine
C:\\\\users\\\\gman\\\\AppData\\\\Roaming\\\\Microsoft\\\\Windows\\\\Start\\
Menu\\\\Programs\\\\7-Zip\\\\7-Zip\\ File\\ Manager.lnk
Type=Application
StartupNotify=true
Icon=EA23_7zFM.0
StartupWMClass=7zfm.exe
```
64bit (x64 with WOW64) wine does not have this issue and the generated .desktop
file will be correct.
eg: /home/gman/.local/share/applications/wine/Programs/7-Zip/7-Zip\ File\
Manager.desktop
```
[Desktop Entry]
Name=7-Zip File Manager
Exec=env WINEPREFIX="/home/gman/.wine" wine
C:\\\\users\\\\gman\\\\AppData\\\\Roaming\\\\Microsoft\\\\Windows\\\\Start\\
Menu\\\\Programs\\\\7-Zip\\\\7-Zip\\ File\\ Manager.lnk
Type=Application
StartupNotify=true
Icon=EA23_7zFM.0
StartupWMClass=7zfm.exe
```
Both are with fresh wine installs with fresh/clean prefixes. Confirmed on
multiple devices.
--
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=54183
Bug ID: 54183
Summary: wineserver crash when running d3d9:visual
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: testcase
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
CC: rbernon(a)codeweavers.com
Distribution: ---
d3d9:visual on this machine breaks somewhere in the middle, apparently while
trying to do mode switches, and leaves the display switched off. Not sure what
triggers it exactly; I've certainly had working runs on other machines. What's
important is that then when d3d9_test.exe exits, it triggers a wined3d crash.
Simple tl;dr version is that set_cursor_pos gets triggered not from a client
request, and tries to access current->process, which crashes.
The backtrace is:
Core was generated by `/home/elizabeth/git/wine64/loader/../server/wineserver
-d'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00005598e8b43ac0 in set_cursor_pos (desktop=desktop@entry=0x5598ea1ce5d0,
x=32767, y=32767) at ../wine/server/queue.c:427
427 if ((device = current->process->rawinput_mouse) && (device->flags &
RIDEV_NOLEGACY))
(gdb) bt
#0 0x00005598e8b43ac0 in set_cursor_pos (desktop=desktop@entry=0x5598ea1ce5d0,
x=32767, y=32767) at ../wine/server/queue.c:427
#1 0x00005598e8b43c7b in set_clip_rectangle
(desktop=desktop@entry=0x5598ea1ce5d0, rect=rect@entry=0x0,
send_clip_msg=send_clip_msg@entry=1) at ../wine/server/queue.c:476
#2 0x00005598e8b43da1 in set_foreground_input (input=0x0,
desktop=0x5598ea1ce5d0) at ../wine/server/queue.c:483
#3 set_foreground_input (input=0x0, desktop=0x5598ea1ce5d0) at
../wine/server/queue.c:480
#4 thread_input_destroy (obj=0x5598ea1ba430) at ../wine/server/queue.c:1106
#5 0x00005598e8b3b144 in release_object (ptr=0x5598ea1ba430) at
../wine/server/object.c:451
#6 release_object (ptr=0x5598ea1ba430) at ../wine/server/object.c:440
#7 0x00005598e8b43800 in msg_queue_destroy (obj=0x5598ea1ae4d0) at
../wine/server/queue.c:1077
#8 0x00005598e8b3b144 in release_object (ptr=0x5598ea1ae4d0) at
../wine/server/object.c:451
#9 release_object (ptr=ptr@entry=0x5598ea1ae4d0) at
../wine/server/object.c:440
#10 0x00005598e8b3224e in release_object_from_handle (obj=0x5598ea1ae4d0) at
../wine/server/handle.c:115
#11 handle_table_destroy (obj=0x5598ea1d3810) at ../wine/server/handle.c:185
#12 0x00005598e8b3b144 in release_object (ptr=0x5598ea1d3810) at
../wine/server/object.c:451
#13 release_object (ptr=0x5598ea1d3810) at ../wine/server/object.c:440
#14 0x00005598e8b3260f in close_process_handles
(process=process@entry=0x5598ea1ce7a0) at ../wine/server/handle.c:197
#15 0x00005598e8b3d990 in process_killed (process=0x5598ea1ce7a0) at
../wine/server/process.c:970
#16 remove_process_thread (process=0x5598ea1ce7a0,
thread=thread@entry=0x5598ea1d4020) at ../wine/server/process.c:1020
#17 0x00005598e8b5b37f in kill_thread (thread=0x5598ea1d4020,
violent_death=<optimized out>, violent_death@entry=0) at
../wine/server/thread.c:1294
#18 0x00005598e8b3dcb0 in kill_process (violent_death=0,
process=0x5598ea1ce7a0) at ../wine/server/process.c:1077
#19 kill_process (process=0x5598ea1ce7a0, violent_death=<optimized out>) at
../wine/server/process.c:1058
#20 0x00005598e8b2d587 in fd_poll_event (event=<optimized out>, fd=<optimized
out>) at ../wine/server/fd.c:542
#21 main_loop_epoll () at ../wine/server/fd.c:636
#22 0x00005598e8b2d7ee in main_loop () at ../wine/server/fd.c:992
#23 0x00005598e8b1ea7d in main (argc=2, argv=0x7ffd26625e48) at
../wine/server/main.c:237
Rémi, do you have any immediate insight on what we should be doing 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.
http://bugs.winehq.org/show_bug.cgi?id=16552
Summary: CreateIoCompletionPort fails in Chromium unit tests
Product: Wine
Version: 1.1.10
Platform: Other
URL: http://chromium.org
OS/Version: other
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: wineserver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_win.cc
contains the code
port_.Set(CreateIoCompletionPort(INVALID_HANDLE_VALUE, NULL, NULL, 1));
DCHECK(port_.IsValid());
...
HANDLE port = CreateIoCompletionPort(file_handle, port_, key, 1);
DCHECK(port == port_.Get());
The DCHECK fires when running one of the Chromium unit tests:
wine Debug/ui_tests.exe
...
001b:Call KERNEL32.CreateFileW(00ed7208
L"\\\\.\\pipe\\chrome.ChromeTestingInterface:8.1",c0000000,00000000,00000000,00000003,40110000,00000000)
ret=010e0220
001b:Ret KERNEL32.CreateFileW() retval=000000c0 ret=010e0220
...
0021:Call KERNEL32.CreateIoCompletionPort(ffffffff,00000000,00000000,00000001)
ret=01a304b3
0021:Ret KERNEL32.CreateIoCompletionPort() retval=000000c8 ret=01a304b3
0021:Call KERNEL32.CreateIoCompletionPort(000000c0,000000c8,00ed5aa0,00000001)
ret=01a30760
trace:ntdll:NtSetInformationFile
(0xc0,0x7cdee318,0x7cdee320,0x00000008,0x0000001e)
0021:Ret KERNEL32.CreateIoCompletionPort() retval=00000000 ret=01a30760
0021:Call KERNEL32.OutputDebugStringA(00ed95a8
"[26:33:1249:FATAL:message_pump_win.cc(428)] Check failed: port == port_.Get().
\r\n") ret=019a7af3
I think it's failing in wineserver for some reason during NtSetInformationFile
in set_completion_info.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.