https://bugs.winehq.org/show_bug.cgi?id=43436
Bug ID: 43436
Summary: Would it be possible to add Mageia 6 back to the
Install page?
Product: Wine-staging
Version: 2.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: arichter(a)lobo.net
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
I would sure like to see Mageia added back to the wine-staging Install page,
Mageia has been very good about keeping up with the stable releases but staging
is where all the fun is.
I have been successfully building RPMS for both i586 and x86_64 under Mageia 6
and would be glad to submit RPMS or SRPMS for both architectures.
Mageia 6 also now supports mock, which is what I have been using to build the
i586 RPMs under x86_64.
I apologize for submitting this as a bug since it's not a bug but I would
either like to see Mageia back under the Install page or contribute built RPMS
and SRPMS to help make it happen.
I'm a bit new to this RPM building thing but the stuff I've made has worked out
for me, and I've tried to be more active in the winedb.
Thank you for your time and efforts, I only want to help on the Mageia side of
things.
--
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=45556
Bug ID: 45556
Summary: libgtk3-nocsd.so.0
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: Ulf.Zibis(a)gmx.de
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
On Ubuntu 18.04 I get:
$ wine --version
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded
(cannot open shared object file): ignored.
wine-3.0.2
Workaround:
sudo apt install libgtk3-nocsd0:i386
--
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=5129
--- Comment #24 from dodog <gaal(a)centrum.sk> ---
(In reply to unxed from comment #23)
> Workaround for Mint 19/Ubuntu 18.04.
>
> --
Thank you very much, this workaround really works. I can confirm this on
Manjaro 17 (arch), Wine 3.12 and Faststone 5.2
--
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=5129
--- Comment #23 from unxed <unxed(a)mail.ru> ---
Workaround for Mint 19/Ubuntu 18.04.
--
0.
If you have any sensitive data stored inside default wineprefix (~/.wine) -
back it up as default wineprefix will be recreated.
1.
sudo apt remove wine1.6 wine64
2.
rm -rf ~/.wine
3.
sudo apt install wine32 winetricks
4.
winetricks comctl32
5.
Run FastStone installer. I recommend you to stick with version 5.2
as more recent ones are buggy under Wine.
For example, "wine FSViewerSetup52.exe".
Don't forget to UNCHECK "run FastStone after installation" checkbox.
6.
cp ~/.wine/drive_c/windows/system32/comctl32.dll ~/.wine/drive_c/Program\
Files/FastStone\ Image\ Viewer/comctr32.dll
7.
cp ~/.wine/drive_c/Program\ Files/FastStone\ Image\ Viewer/FSViewer.exe
~/.wine/drive_c/Program\ Files/FastStone\ Image\ Viewer/FSViewer.exe.bak
8.
Use any bin/hex editor to replace all "comctl32.dll" strings in FSViewer.exe
with "comctr32.dll".
9.
Run "winecfg" and set comctl32.dll as INTERNAL (Wine).
--
Works for me under Mint 19 x64; should work under Ubuntu 18.04 also.
Wine version is 3.0, system default.
--
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=45555
Bug ID: 45555
Summary: hearthstone installer battle.net crashes
Product: Wine
Version: 3.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mladen.adamovic(a)gmail.com
Distribution: ---
Created attachment 61979
--> https://bugs.winehq.org/attachment.cgi?id=61979
log file
hearthstone installer battle.net crashes
--
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=44735
Bug ID: 44735
Summary: Star of Plants Vs zombies have a 3 minutes delay when
system's net connection is online.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: amie1972(a)163.com
Distribution: ---
net connection results a game starting delay.
--
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=2082
--- Comment #170 from Saulius K. <saulius2(a)gmail.com> ---
Found some MSDN article called "Redirecting GDI, DirectX, and WPF applications"
[4]. How do devs think, can it bring some simplicity for the situation?
--- quote ---
Mixed DirectX and GDI Windows
The other reasonably common rendering to a top level window involves mixing
DirectX and GDI. There are two forms of "mixing" here, one is perfectly fine,
and the other is problematic.
_The form of mixing that is fine_ is when there is a window tree of the top
level HWND and child HWNDs (and further children, etc), where each individual
HWND is either rendered by DirectX or by GDI. In this situation, the
redirection component of the DWM forms its own "composition tree" where each
node in the tree represents a node or a set of "homogenously rendered nodes" in
the "window tree" rooted at the top level HWND. Rendering occurs by having
each of these render to their own surface, and then compositing this tree of
surfaces to the desktop. Thus, mixed DirectX and GDI rendering works well, so
long as the boundary between them is at least at the child HWND level.
_The form of mixing that _doesn't work well_ is when an application uses
DirectX and GDI to target the same HWND. This has never been a supported
scenario with DirectX, but there have been scenarios where it has happened to
work. Under the DWM, this is much more problematic, because there can be no
guarantee of ordering between the DirectX and the GDI rendering. This is most
troublesome when GDI and DirectX are not only rendering to the same HWND, but
to overlapping areas of the same HWND. As such, this usage pattern is not
supported. Note that there is an alternative that can often work for an
application -- DirectX is capable of handing back a DC to a DirectX surface,
and applications can perform GDI rendering to that DC. From the DWM's
perspective, that DirectX surface remains purely rendered by DirectX, and all
is well.
--- quote ---
[4]
https://blogs.msdn.microsoft.com/greg_schechter/2006/05/03/redirecting-gdi-…
--
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=7284
lsh(a)ccxx.cx changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lsh(a)ccxx.cx
--- Comment #85 from lsh(a)ccxx.cx ---
Bug is present in wine-3.13 (Staging). Regression?
--
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=2082
Jimmy Christensen <jichr86(a)dusted.dk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jichr86(a)dusted.dk
--- Comment #169 from Jimmy Christensen <jichr86(a)dusted.dk> ---
But is also present in version 3.0, tried with Diablo, the intro movies render,
the menu does not (blank screen), if I blindly enter the game, loading screen
and gameplay is displayed.
--
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=8606
spottedowl <spambuster300(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |spambuster300(a)gmail.com
--- Comment #41 from spottedowl <spambuster300(a)gmail.com> ---
Wine 3.0.2 with version 1.7.5.7 of Joint Ops Typhoon Rising still produces the
"Unable to create a network socket" error upon load. If you install from disc
and don't update you can at least run the single player training mode, but
updating the game makes this error appear upon loading the 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.