http://bugs.winehq.org/show_bug.cgi?id=24846
Summary: SecureCRT: Pop-up menu list flashes
Product: Wine
Version: 1.3.5
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lukasz.wojnilowicz(a)gmail.com
Created an attachment (id=31435)
--> (http://bugs.winehq.org/attachment.cgi?id=31435)
Image showing the problem
Steps to reproduce:
1) remove ~/.wine
2) winetricks gecko
2) install SecureCRT
3) wine SecureCRT.exe
4) unfold pop-up menu as shown in attachment
Behaviour:
Pop-up menu list flashes.
Expected behaviour:
Pop-up menu list shouldn't flash.
--
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=20962
Summary: Starting Secunia PSI starts a window but with no
contents
Product: Wine
Version: 1.1.34
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: leighmanthegreat(a)hotmail.com
Created an attachment (id=25129)
--> (http://bugs.winehq.org/attachment.cgi?id=25129)
Terminal output
Installation works fine but when opening window it just picks up its filling
from the desktop below.
Closing it results in a crash dialog
--
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=32445
Bug #: 32445
Summary: PuTTY window does not receive focus when "Allow window
manager to control windows" option disabled
Product: Wine
Version: 1.5.19
Platform: x86-64
URL: http://www.chiark.greenend.org.uk/~sgtatham/putty/
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
I noticed this issue testing PuTTY 0.62 with wine-1.5.19-74-g4bb92e1. Testing
on Lubuntu 11.10 (OpenBox 3.5.0 WM).
When the "Allow the window manager to control the windows" option has been
disabled using winecfg, the PuTTY terminal window does not receive keyboard
input. Instead the console window which you ran putty.exe from receives input.
That only applies to the PuTTY terminal window, not the initial settings
window. It also only applies when *not* in virtual desktop mode.
To reproduce:
- Disable "Allow the window manager to control the windows" in winecfg
- Download and run putty.exe. The PuTTY Configuration window appears. Note
that initially it does not seem to have focus; the window title bar is grey not
blue. However the window does actually have focus and receives keyboard input.
- Connect to a server. E.g. enter telehack.com for Host Name, Telnet for
connection type and click the Open button.
- The terminal window appears after a few seconds. It seems to be focused
(title bar blue) but even if you click in the window, the characters you type
appear in the console. (If you activate another window before clicking in the
PuTTY one, input goes to that window instead.)
--
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=51675
Bug ID: 51675
Summary: Divinity Original Sin 2 doesn't start with wine 6.15
Product: Wine
Version: 6.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stefanescu.a(a)mail.com
Distribution: ---
Divinity Original Sin 2 Definitive Edition and Classic Edition doesn't start
with wine 6.15. There is no message from the game, it just makes a CrashDump
file.
With Wine 6.0 stable the game starts and works just fine.
On Wine 6.15 the game crashes with this message:
00f8:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
00f8:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpWithHandleData
Monitored process exited.
Initial process has exited (return code: 1280)
All monitored processes have exited.
Exit with returncode 1280
--
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=43370
Bug ID: 43370
Summary: Origin fails to start, repeats the same message over
and over
Product: Wine
Version: 2.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: haakobja(a)gmail.com
Distribution: ---
Hi,
I tried Origin with Wine 2.12-Staging, and while it installs just fine I cannot
get to the log in. When I open Origin the debug log fills with the same line:
err:d3d:context_reacquire Acquired context 0x66b7418 instead of 0x66c17b0.
I'm currently using Fedora 26 x86_64 with Mesa 17.1.5 and this happens in both
the 32 bit and the 64 bit wine prefix.
--
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=52271
Bug ID: 52271
Summary: In the game Max Payne 3 (purchased from Rockstar Games
Launcher) cursor during the game runs away to the
second monitor.
Product: Wine
Version: 7.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jon9097(a)gmail.com
Distribution: ---
In the game Max Payne 3 (purchased from Rockstar Games Launcher) cursor during
the game runs away to the second monitor.
Arch Linux
--
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=52122
Bug ID: 52122
Summary: Since 6.21 cups printers are not detected
Product: Wine
Version: 6.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: spooler
Assignee: wine-bugs(a)winehq.org
Reporter: andreas(a)sassermann.de
Distribution: ---
Created attachment 71153
--> https://bugs.winehq.org/attachment.cgi?id=71153
winespool debug output
Since the upgrade to 6.21 the cups printers are no longer recognized.
Reproduce:
start notepad.exe
Open printdialog, confirm error message about no available printers.
Printer selection is empty.
After reverting to 6.16 the printers loads the printers as expected.
System:
Manjaro, Kernel 5.10.79-1-MANJARO, KDE, CUPS 2.3.3op2
--
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=52047
Bug ID: 52047
Summary: not all joysticks show up in wine
Product: Wine
Version: 6.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: joy.cpl
Assignee: wine-bugs(a)winehq.org
Reporter: erlofgrey(a)gmail.com
Distribution: ---
Created attachment 71058
--> https://bugs.winehq.org/attachment.cgi?id=71058
part of dmesg, terminal output, 2 screenshots
in wine 6.21 i see only 2 joysticks in joy.cpl instead of 3, i checked wine
6.18 and there i see all 3 and additionally (js) and (event) versions in the
list.
i checked additionally wine-ge between 6.18 and 6.21, last working was 6.19
there and broken with 6.20.
--
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=51518
Bug ID: 51518
Summary: NovaRO crashes when doing Monster Hunter quest
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alandms123(a)gmail.com
Distribution: ---
Created attachment 70360
--> https://bugs.winehq.org/attachment.cgi?id=70360
crash-log-stripped.txt
The game crashes when trying to do some quests, but in specific the Monster
Hunter quest. The "dispatch_exception EXCEPTION_ACCESS_VIOLATION exception
(code=c0000005) raised" got my attention when crashing.
Also the crash isn't always reproducible, I would it crashes 95% of time at the
same part, but there is a 5% chance that the game doesn't crashes at all (the
crashes aren't experienced by Windows users).
Also there is a "workaround" to decrease (just a little) the chances of the
game crashing that is running the game with WINEDEBUG, as:
WINEDEBUG=warn+all,-d3d,-d3d_perf,-wgl,-ntdll wine NovaRO.exe
as said by a developer of the game it "Debug output is required to avoid a race
condition in the client."
steps to reproduce (after the game already installed, account and character
already created):
- type "@go mh" (without quotes) in the chat
- go to the entrance at your front
- select "play cutscene" option
--
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=51239
Bug ID: 51239
Summary: ndis.sys:ndis fails when network interfaces come and
go
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ndis.sys
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ndis.sys:ndis fails when network interfaces come and go. This shows up at least
as this failure:
https://test.winehq.org/data/patterns.html#ndis.sys:ndis
ndis.c:122: Test failed: GetIfEntry2 failed
But likely also causes these:
ndis.c:124: Test failed: Wrong ServiceName
ndis.c:77: Test failed: Wrong permanent address
ndis.c:84: Test failed: Wrong current address
So this can cause failures when running it on a machine that has Docker/Podman,
QEmu (particularly if it acts as a TestBot VM host), VPNs (if the connection
gets reset at the wrong time), etc.
--
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.