https://bugs.winehq.org/show_bug.cgi?id=44079
Bug ID: 44079
Summary: Starcraft Remaster lose ability to select individual
units from groups after alt+tabbing.
Product: Wine
Version: 2.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: brennanruthardt(a)gmail.com
Distribution: ---
Using wine-staging, version 2.21
4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64 GNU/Linux
Playing StarCraft remaster. Downloaded executable from official Blizzard site.
Installed with wine. I have also installed all optional dependencies as per
pacman -Qi wine-staging
Make a control group for units (i.e. select units, press CTRL+<number>, those
units are hotkeyed to select by pressing <number>). If you then ALT+TAB out of
the game and ALT+TAB back in you cannot select individuals from that group.
*Selecting an individual unit with the mouse then selects that entire unit's
control group, instead of the individual unit.
*Selecting the group and then clicking on an individual unit (through the UI or
clicking the unit itself) selects the entire group again, and not the
individual unit.
*Selecting the group and then shift+clicking to remove units from the group has
no effect.
I use GDM. Pressing the super key and then selecting another program, then
doing this again to return to StarCraft does not produce this behavior.
Current Workaround: Saving your game, and loading it again fixes the behavior
until you ALT+TAB again. Obviously this isn't a feasible workaround for
multiplayer games.
--
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=8051
Alexandr Oleynikov <sashok.olen(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sashok.olen(a)gmail.com
--- Comment #145 from Alexandr Oleynikov <sashok.olen(a)gmail.com> ---
Bug is still present in 2.21-staging.
--
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=44068
Bug ID: 44068
Summary: Guitar Pro 7: incorrect save
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kreopt(a)gmail.com
Distribution: ---
Guitar Pro 7 saves files in zipped XML. The problem is in representation of
floating point numbers: Windows version saves it in XXX.YYY format while Wine
uses XXX,YYY format. As a result - GP crashes when trying to open file saved on
Linux with Wine
--
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=44069
Bug ID: 44069
Summary: Guitar Pro 7: unable to copy-paste
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kreopt(a)gmail.com
Distribution: ---
when trying to copy-paste some chunk of score, GP complains about paste fail
for some reason
--
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=40005
Bug ID: 40005
Summary: ElicaLogo doesn't show the Help Library
Product: Wine
Version: 1.9.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jotape1960(a)yahoo.com
Distribution: ---
ElicaLogo is a variation of the well-known Logo programming language (the great
turtle and its graphic world).
This software was made to Windows XP enviroment and its last upgrade was at
2003.
This software comes with a very large Help Menu, which should be diplayed on a
dockable window panel. It has a lot of text and images and samples codes to
teach all about the internal ElicaLogo commands.
In Windows XP, Vista, 7 and 8, it works so fine, all the Help menu is
displayed.
In Linux (Ubuntu and Lubuntu) we can not to see any on the Help menu window.
The ElicaLogo Help Menu is on a directory with a lot of text, jpg and HTML
format 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=43441
Bug ID: 43441
Summary: NVAPI unimplemented functions
Product: Wine-staging
Version: 2.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: byi5000(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Since the staging part of wine just started working on the nvapi, i have
"collected" more common nvapi calls. In this case none of the reported
functions are breaking, but asked for by games.
Rise of the Tomb Raider and Tomb Raider 2013:
fixme:nvapi:unimplemented_stub function 0xdc6dc8d3 is unimplemented!
Spintires:
fixme:nvapi:unimplemented_stub function 0x6c2d048c is unimplemented!
Beamng.Drive:
fixme:nvapi:unimplemented_stub function 0x694d52e is unimplemented!
--
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=43965
Bug ID: 43965
Summary: Project ERROR: Cannot run compiler 'g++'. Maybe you
forgot to setup the environment?
Product: Wine
Version: 2.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alpha_one_x86(a)first-world.info
Distribution: ---
Hi,
I have copied Qt 5.9.1 to my wine and put it into the PATH, I have this bug:
wine qmake
fixme:file:FindFirstFileExW flags not implemented 0x00000002
Project ERROR: Cannot run compiler 'g++'. Maybe you forgot to setup the
environment?
g++ is well detected:
wine g++
g++.exe: fatal error: no input files
compilation terminated.
* same problem with official and compiled with mingw version
* no problem with full windows into qemu
Cheers.
--
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=44006
Bug ID: 44006
Summary: Can't use valgrind with wine-staging (works with
vanilla wine)
Product: Wine
Version: 2.17
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, valgrind
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Gentoo
While looking at https://github.com/Winetricks/winetricks/issues/810, I noticed
that wine-staging has some memory corruption in msxml3 that does not occur
under wine. I tried running the dotnet35sp1 installer under valgrind, which
quickly crashed.
I then ran a more simple test (scripts/suppressions at
https://github.com/austin987/wine-valgrind-scripts)
$ . vg-wrapper.sh
$ wine start /min winemine
$ valgrind wine notepad
works fine, only output is:
austin@austin2:~$ valgrind wine notepad
preloader: Warning: failed to reserve range 00110000-68000000
preloader: Warning: failed to reserve range 7f000000-82000000
If I try the same under wine-staging, however:
$ . vg-wrapper.sh
$ wine-staging start /min winemine
$ valgrind wine-staging notepad
I get a nastly valgrind crash:
austin@austin2:~$ valgrind wine-staging notepad
preloader: Warning: failed to reserve range 00110000-68000000
preloader: Warning: failed to reserve range 7f000000-82000000
valgrind: m_debuginfo/debuginfo.c:551 (check_CFSI_related_invariants):
Assertion 'cfsi_fits' failed.
host stacktrace:
==9003== at 0x58039CF7: show_sched_status_wrk (m_libcassert.c:355)
==9003== by 0x58039E01: report_and_quit (m_libcassert.c:426)
==9003== by 0x58039EE3: vgPlain_assert_fail (m_libcassert.c:492)
==9003== by 0x5806855E: check_CFSI_related_invariants (debuginfo.c:551)
==9003== by 0x5806855E: di_notify_ACHIEVE_ACCEPT_STATE (debuginfo.c:766)
==9003== by 0x5806855E: vgPlain_di_notify_mmap (debuginfo.c:1063)
==9003== by 0x58090184: vgModuleLocal_generic_PRE_sys_mmap
(syswrap-generic.c:2388)
==9003== by 0x580C199A: vgSysWrap_x86_linux_sys_mmap2_before
(syswrap-x86-linux.c:989)
==9003== by 0x5808D022: vgPlain_client_syscall (syswrap-main.c:1857)
==9003== by 0x58089E90: handle_syscall (scheduler.c:1126)
==9003== by 0x5808B5C6: vgPlain_scheduler (scheduler.c:1443)
==9003== by 0x58099223: thread_wrapper (syswrap-linux.c:103)
==9003== by 0x58099223: run_a_thread_NORETURN (syswrap-linux.c:156)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 9003)
==9003== at 0x4018F10: mmap (mmap.c:32)
==9003== by 0x4006806: _dl_map_segments (dl-map-segments.h:90)
==9003== by 0x4006806: _dl_map_object_from_fd (dl-load.c:1183)
==9003== by 0x4008A19: _dl_map_object (dl-load.c:2199)
==9003== by 0x40138B7: dl_open_worker (dl-open.c:226)
==9003== by 0x43B09C6: _dl_catch_error (dl-error-skeleton.c:198)
==9003== by 0x40133A1: _dl_open (dl-open.c:649)
==9003== by 0x4447C72: dlopen_doit (dlopen.c:66)
==9003== by 0x43B09C6: _dl_catch_error (dl-error-skeleton.c:198)
==9003== by 0x44484B1: _dlerror_run (dlerror.c:163)
==9003== by 0x4447D2D: dlopen@@GLIBC_2.1 (dlopen.c:87)
==9003== by 0x404522E: wine_dlopen (loader.c:1051)
==9003== by 0x40458F5: wine_init (loader.c:977)
==9003== by 0x7C000C01: main (in /usr/lib64/wine-staging-2.17/bin/wine)
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.
Note, I only had wine-staging 2.17 installed, I can retest in 2.20 if needed. I
havne't filed a valgrind bug, as it seems more likely to be a staging bug, but
I can file one upstream if needed.
--
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=43946
Bug ID: 43946
Summary: wineboot crashes with stack smashing on aarch64
Product: Wine
Version: 2.19
Hardware: aarch64
OS: Linux
Status: NEW
Keywords: download, regression, source
Severity: normal
Priority: P2
Component: loader
Assignee: nerv(a)dawncrow.de
Reporter: austinenglish(a)gmail.com
Regression SHA1: 27e92e550c2b86d5ebd4966926c1fcde03838dcc
Distribution: Ubuntu
austin@gcc116:~/wine-git$ rm -rf ~/.wine ; ./wine wineboot
wine: created the configuration directory '/home/austin/.wine'
*** stack smashing detected ***: C:\windows\system32\rundll32.exe terminated
wine: Assertion failed at address 0x7f966f6af8 (thread 0010), starting
debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 15 100") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
fixme:seh:RtlUnwind Not implemented on ARM64
err:winediag:nodrv_CreateWindow Application tried to create a window, but no
driver could be loaded.
err:winediag:nodrv_CreateWindow Make sure that your X server is running and
that $DISPLAY is set correctly.
*** stack smashing detected ***: C:\windows\syswow64\rundll32.exe terminated
wine: Assertion failed at address 0x7fa289caf8 (thread 0016), starting
debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 21 56") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
fixme:seh:RtlUnwind Not implemented on ARM64
wine: configuration in '/home/austin/.wine' has been updated.
Noticed on GCC Compiler farm machine.
--
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=43332
Bug ID: 43332
Summary: rsaenh: Warning and notes while building (GCC 7.1.1)
Product: Wine
Version: 2.12
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: rsaenh
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
rsaenh.c: In function ‘create_container_key.constprop’:
rsaenh.c:156:23: warning: ‘%s’ directive writing up to 259 bytes into a region
of size 235 [-Wformat-overflow=]
#define RSAENH_REGKEY "Software\\Wine\\Crypto\\RSA\\%s"
^
rsaenh.c:156:23: note: in definition of macro ‘RSAENH_REGKEY’
#define RSAENH_REGKEY "Software\\Wine\\Crypto\\RSA\\%s"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rsaenh.c:1102:5: note: ‘sprintf’ output between 26 and 285 bytes into a
destination of size 260
sprintf(szRSABase, RSAENH_REGKEY, pKeyContainer->szName);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
wine-2.12-103-g989a9dc917
--
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.