https://bugs.winehq.org/show_bug.cgi?id=52491
Bug ID: 52491
Summary: SpaceDesk: Error when trying to connect to the server
now but it worked in 6.10 and below
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jota0222(a)hotmail.com
Distribution: ---
Created attachment 71785
--> https://bugs.winehq.org/attachment.cgi?id=71785
Log Of SpaceDesk Runinng
After the release of stable 7.0.0, I noticed that SpaceDesk stoped working and
then I tried some older versions versions, none of the listed to register the
apps in the WineHQ page worked (6.21 and above), however it worked in all the
ones below 6.10. I didn't try with the ones in between, so I don't really know
when the bug was introduced exactly.
The app doesn't throw exceptions or show error in logs, the log attached is
basically the same in both 6.10 and 7.0.0 versions.
I also tried with winedbg but if I dissable $BreakOnFirstChance it never stops
on any exception and the log finish up being the same as the one attached (at
least doesn't looks like it's showing things related to the issue). And if I
run it with $BreakOnFirstChance set as 1, it's impossible to reach the moment
of in which the error occurs due to al the exceptions in which it stops before
to even show the window.
This image shows the error:
https://paste.pics/FTUXV
--
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=38780
Bug ID: 38780
Summary: AArch64 platforms: register X18 must remain reserved
for Wine to run 64-bit ARM Windows applications
(Distro aarch64 toolchains need '-ffixed-x18' default,
loader/libc/userland)
Product: Wine
Version: 1.7.45
Hardware: aarch64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
split off from bug 38719 ("64-bit ARM Windows applications from Windows SDK for
Windows 10 crash when accessing TEB/PEB members (AArch64 platform specific
register X18 must be reserved for TEB)")
Resolution is 'upstream' here, the Wine part is bug 38719
http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055b/IHI0055B_aapcs64.…
Chapter 5 "THE BASE PROCEDURE CALL STANDARD"
--- quote ---
The role of register r18 is platform specific.
If a platform ABI has need of a dedicated general purpose register to carry
interprocedural state (for example, the thread context) then it should use this
register for that purpose. If the platform ABI has no such requirements, then
it should use r18 as an additional temporary register.
The platform ABI specification must document the usage for this register.
Note
Software developers creating platform independent code are advised to avoid
using r18 if at all possible. Most compilers provide a mechanism to prevent
specific registers from being used for general allocation; portable hand-coded
assembler should avoid it entirely. It should not be assumed that treating the
register as callee saved will be sufficient to satisfy the requirements of the
platform. Virtualization code must, of course, treat the register as they would
any other resource provided to the virtual machine.
--- quote ---
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.
https://bugs.winehq.org/show_bug.cgi?id=47406
Bug ID: 47406
Summary: add support for debug symbols is separate files
Product: Wine
Version: 4.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
<will be a bit ranty>
One on the "installation options" on Gentoo is 'splitdebug'.
It allows to keep debug symbols in separate files (and potentially keep them
compressed). gdb supports it (AFAICT) seamlessly. While addr2line doesn't seem
to supports it, the one from elfutils does.
I don't know where Gentoo got the idea, but given gdb and elfutils, it's likely
more wide-spread than Gentoo family.
So, would you consider adding support for it in winedbg ?
--
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=46777
Bug ID: 46777
Summary: Two Worlds 2 crashing on start [REGRESSION]
Product: Wine
Version: 4.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: timofeevsv1989(a)gmail.com
Distribution: ---
Created attachment 63791
--> https://bugs.winehq.org/attachment.cgi?id=63791
Two Worlds 2 crash. Console out.
Two Worlds 2 crashing on start. In older wine (4.0) on load screen.
On old wine 1.1.39 everything was OK
--
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=53319
Bug ID: 53319
Summary: robot battle game extremely slow after wine version
7.11 and above
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: evren320(a)hotmail.com
Distribution: ---
Robot Battle 1.4 game is slow on wine version 7.11 and above.
Game works fine with wine 7.10 and 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=50998
Bug ID: 50998
Summary: Failed to open error Word 2007 (c0000135)
Product: Wine-staging
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pierce.adam.randall(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Since 6.5, I'm not able to open Word 2007.
I get the following errors when I try to open it in terminal:
wine: failed to open "[path redacted]/drive_c/Program Files/Microsoft
Office/Office12/WINWORD.exe": c0000135
0094:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003
Not much other than that.
I'm using Arch Linux. Kernel 5.11.13.
The program works on 6.4, but not 6.5 or 6.6. I also ran into this bug using
non-staging version of 6.5.
--
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=49852
Bug ID: 49852
Summary: Performance regression in "msvcrt: Use correct code
page in _write when outputing to console."
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: martin(a)martin.st
Distribution: ---
Created attachment 68190
--> https://bugs.winehq.org/attachment.cgi?id=68190
Test sample
Since 081d25d4b989c732d301b786311c034132c8d7a3, "msvcrt: Use correct code page
in _write when outputing to console.", a test app (that prints a lot to stdout)
had an around 10-20x slowdown.
Before, "time wine64 ihateeh-x86_64.exe > /dev/null 2>&1" ran in around 1
second, after that commit it takes 15 seconds. (At some later point, it has
regressed further to 25 seconds. The corresponding testcase on aarch64 used to
run in 3 seconds, after the commit it takes 60, and with current master takes
around 120 seconds.)
--
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=51603
Bug ID: 51603
Summary: All applications were run with a crash dialog, and can
not run any application after re-create the .wine
prefix.
Product: Wine-staging
Version: 6.14
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: avenjames(a)live.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Created attachment 70452
--> https://bugs.winehq.org/attachment.cgi?id=70452
Backtrace from the crash dialog.
Machine: MacBook Pro Retina-2015mid with OSX 10.14.6 Mojave
I remember that last time I was using OSX 10.13, I got the same problem.
With the Wine-staging from Gcenx's build. But after deleted the .wine and run
the Wine-staging again, it was back to work normally,
But after playing two games: Red Alert 2 and Diablo II,
I don't know if I was playing too long, games was crashed finally and then I
run "wineserver -k" to kill all the wine-preloader processes,
Then after awhile I wanna to play the game again but it was crashed on the
halfway,
then I start the Terminal to input:
winecfg
it was showing:
-----------------------------------------------------------------------------
Last login: Sat Aug 14 16:36:30 on ttys000
192:~ avenue$ winecfg
0024:fixme:esync:do_esync eventfd not supported on this platform.
002c:fixme:esync:do_esync eventfd not supported on this platform.
002c:fixme:winediag:LdrInitializeThunk wine-staging 6.14 is a testing version
containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when
filing bug reports on winehq.org.
wine: Unhandled page fault on read access to 0000000000000000 at address
00000003AF6DF950 (thread 002c), starting debugger...
0034:fixme:esync:do_esync eventfd not supported on this platform.
0040:fixme:esync:do_esync eventfd not supported on this platform.
0040:err:display:prepare_devices Failed to remove monitor
0040:err:display:macdrv_init_monitor Failed to initialize monitor
0040:err:display:cleanup_devices Failed to remove GPU
0040:err:ole:start_rpcss Failed to open service manager
0034:err:display:cleanup_devices Failed to remove GPU
0034:err:display:prepare_devices Failed to remove monitor
0034:err:display:macdrv_init_monitor Failed to initialize monitor
0034:err:display:cleanup_devices Failed to remove GPU
0034:fixme:thread:get_thread_times not implemented on this platform
0058:fixme:esync:do_esync eventfd not supported on this platform.
0060:fixme:esync:do_esync eventfd not supported on this platform.
0040:err:ole:start_rpcss Failed to open service manager
0060:err:display:cleanup_devices Failed to remove GPU
0060:err:ole:start_rpcss Failed to open service manager
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49:
Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353:
Error: Unknown compression scheme encountered for file
'/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49:
Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353:
Error: Unknown compression scheme encountered for file
'/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist'
0024:err:display:cleanup_devices Failed to remove GPU
0070:fixme:esync:do_esync eventfd not supported on this platform.
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49:
Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353:
Error: Unknown compression scheme encountered for file
'/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49:
Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353:
Error: Unknown compression scheme encountered for file
'/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist'
0070:err:display:cleanup_devices Failed to remove GPU
0078:fixme:esync:do_esync eventfd not supported on this platform.
0078:err:display:cleanup_devices Failed to remove GPU
0078:err:display:prepare_devices Failed to remove monitor
0078:err:display:macdrv_init_monitor Failed to initialize monitor
0078:err:display:cleanup_devices Failed to remove GPU
0060:err:display:prepare_devices Failed to remove monitor
0060:err:display:macdrv_init_monitor Failed to initialize monitor
0060:err:display:cleanup_devices Failed to remove GPU
0078:err:winecfg:open_mountmgr failed to open mount manager err 2
192:~ avenue$ 0060:err:ole:start_rpcss Failed to open service manager
---------------------------------------------------------------------------------
Then I tried to input: rm -rf .wine and run again the winecfg to recreate the
files,
it said:
----------------------------------------------------------------------------------
192:~ avenue$ winecfg
wine: created the configuration directory '/Users/avenjames/.wine'
0024:fixme:esync:do_esync eventfd not supported on this platform.
002c:fixme:esync:do_esync eventfd not supported on this platform.
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
002c:fixme:winediag:LdrInitializeThunk wine-staging 6.14 is a testing version
containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when
filing bug reports on winehq.org.
wine: Unhandled page fault on read access to 0000000000000000 at address
00000003AF6DF950 (thread 002c), starting debugger...
002c:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 40 48" (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: could not load kernel32.dll, status c0000135
192:~ avenue$
----------------------------------------------------------------------------------
Then WINE CAN NOT RUN ANY APPLICATION AGAIN,
even tried brew re-install the wine but it was still couldn't make it.
attached backtrace.txt for checking.
--
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=13685
Summary: Anarchy Online is very slow in certain areas (< 3fps or
0)
Product: Wine
Version: CVS/GIT
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: krause.marcel(a)gmx.net
It's something that's bugging me for a good while, and is also being mentioned
in the AppDB article for the game. As I said there it can be "worked around" by
using the commercial cedega software, which has other minor problems too, but
nothing compared to the slowness under wine.
1. download the free client using bittorrent:
http://torrent.funcom.com/torrents/AnarchyOnline_17.6.1_EP0.exe.torrent
2. register a free account: http://register.funcom.com/
3. Start the game, talk to the neutral recruiter at the island and take the
Wompah (teleporter) to Borealis, which will leave you in complete graphical
laggyness.
You can also notice the laggyness at the Unicorn Outpost (needs paid expansion
content), playershops in the guild cities (paid content too), and a few more
places. All of these places are frequently used by the players and visiting
them is a major pain of course, but as they're the central places in game, you
can't really get around on the long run.
It's not my system causing the lag though, as it works fine with the cedega
software.
Specs are:
Athlon X2 5000+
2Gb Ram
GeForce 8600GT@256MB
400GB WD harddisk
16MBit/s internet connection
Regards,
Marcel Krause
--
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.