https://bugs.winehq.org/show_bug.cgi?id=41112
Bug ID: 41112
Summary: Wine does not open .log files automatically
Product: Wine
Version: 1.9.16
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 00cpxxx(a)gmail.com
Distribution: Debian
When running CPU-Z sometimes it will fail to load its driver and then will ask
if you want to see the log file. This will always fail with a second message
box saying the file was not found. By running +process we can see this:
trace:process:create_process_impl app (null) cmdline
L"\"C:\\users\\wine\\Temp\\\\cpuz_driver_8.log\""
Then I opened the .exe and changed .log for .txt and voilà , the file was opened
in notepad.
trace:process:create_process_impl app (null) cmdline
L"\"C:\\users\\wine\\Temp\\\\cpuz_driver_8.txt\""
...
trace:process:create_process_impl starting
L"C:\\windows\\system32\\notepad.exe" as Win32 binary (0x10000000-0x1002f000,
arch 014c, fakedll)
Is it possible to make .log files also open in notepad?
--
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=39871
Bug ID: 39871
Summary: Evernote: Fatal error dialog is unable to open the log
file
Product: Wine
Version: 1.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: robert.munteanu(a)gmail.com
Distribution: ---
Created attachment 53235
--> https://bugs.winehq.org/attachment.cgi?id=53235
Fatal error dialog with the 'Open Log' button
After a crash Evernote presents a dialog which can be used to send feedback to
the dev team and also open the error log. When trying to open the error log I
get a dialog which says that
There is no Windows program configured to open this type of file
The terminal output after pressing the button is only
fixme:exec:SHELL_execute flags ignored: 0x00004100
--
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=25872
Summary: dxdiag doesn't support /t option, needed by Guild Wars
'test system' button
Product: Wine
Version: 1.3.12
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
This is the next problem after bug 25871.
Guild wars installs nicely, but if you press 'test system', you see
...
fixme:dxdiag:ProcessCommandLine /t unimplemented
--
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=42026
Bug ID: 42026
Summary: Monkey Island 2: Special Edition crashes to a black
window on launch.
Product: Wine
Version: 2.0-rc2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thedoogster(a)gmail.com
Distribution: ---
Created attachment 56488
--> https://bugs.winehq.org/attachment.cgi?id=56488
wine Monkey2 &> log.txt
When I use WINE to start Monkey Island 2: Special Edition (from GOG), the
screen turns black. Pressing ESC closes the game (with the full-screen, black
window), and I can see the attached output in my terminal.
I should be able to switch to another desktop and get a debug trace when the
black game window is on the screen, if you'd like me to do that.
I'm using 375.26 of NVidia's drivers. While I started having WINE issues
(including this one) after the driver upgrade, and I've recently had similar
issues with Shantae: Pirate's Curse (also from GOG), everything other than
WINE seems to be working fine.
--
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=21666
Summary: Heavy Metal Pro fails to print Record Sheet
Product: Wine
Version: 1.1.38
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquitsnake(a)gmx.net
All other print options work fine, but the record sheet fails with "Error
Number 6: Overflow". No suspicious console log.
--
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=34331
Bug #: 34331
Summary: Toolbar buttons can be activated without a proper
click
Product: Wine
Version: 1.6
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: blubban(a)gmail.com
Classification: Unclassified
Created attachment 45697
--> http://bugs.winehq.org/attachment.cgi?id=45697
Minimized (110 lines) testcase; includes source and 32bit binary
Steps to reproduce:
1. Open the attached testcase, or anything else with a toolbar (I did nothing
weird with the testcase).
2. Click and hold the mouse on any non-disabled toolbar button
3. Move the mouse to any other toolbar button, disabled or not; release the
mouse
Expected result: The button is not activated, since the mouse was depressed
while hovering over another button. This is also the result on Windows 7 64bit.
Actual result: The button is activated. This can even be done if the button is
disabled, which can give all kinds of strange results in apps that assume
disabled buttons are not triggerable.
To guarantee there is no weird config nearby, I have tested it with a live CD
in a virtual machine. Linux Mint 15 MATE, 64bit; wine1.6-0ubuntu1. I'd use 1.7
if it was in the PPA, but I don't think I have enough RAM to compile Wine on
that VM.
--
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=32482
Bug #: 32482
Summary: Windows Sysinternals "PsInfo" tool fails to retrieve
"Physical Memory" value from
"HKLM\\Hardware\\ResourceMap\\System Resources"
registry key
Product: Wine
Version: 1.5.19
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Classification: Unclassified
Hello folks,
Windows Sysinternals "PsInfo" tool fails to query for some system properties...
Making this bug about "Physical Memory".
Output:
--- snip ---
$ wine ./PsInfo.exe
PsInfo v1.77 - Local and remote system information viewer
Copyright (C) 2001-2009 Mark Russinovich
Sysinternals - www.sysinternals.com
Querying information for nexus4...fixme:ole:CoInitializeSecurity
((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
System information for \\nexus4:
Uptime: Error reading uptime
Kernel version: Microsoft Windows XP, Uniprocessor Free
Product type: Professional
Product version: 5.1
Service pack: 3
Kernel build number: 2600
Registered organization:
Registered owner:
IE version: 6.0000
System root: C:\windows
Processors: 4
Processor speed: 2.6 GHz
Processor type: Intel(R) Pentium(R) 4 CPU
Physical memory: 0 MB
Video driver:
--- snip ---
Trace log (processor info = ok, physmem = missing):
--- snip ---
...
0024:Call advapi32.RegOpenKeyExW(80000002,0042f520
L"Hardware\\Description\\System\\CentralProcessor\\0",00000000,00020019,0032f96c)
ret=00404a33
0024:Ret advapi32.RegOpenKeyExW() retval=00000000 ret=00404a33
0024:Call advapi32.RegQueryValueExW(00000054,0042f510
L"~MHz",00000000,0032f970,0043c0e4,0032f968) ret=00404a58
0024:Ret advapi32.RegQueryValueExW() retval=00000000 ret=00404a58
0024:Call advapi32.RegQueryValueExW(00000054,0042f4e8
L"ProcessorNameString",00000000,0032f970,0043d538,0032f968) ret=00404a81
0024:Ret advapi32.RegQueryValueExW() retval=00000000 ret=00404a81
0024:Call advapi32.RegCloseKey(00000054) ret=00404a95
0024:Ret advapi32.RegCloseKey() retval=00000000 ret=00404a95
0024:Call advapi32.RegOpenKeyW(80000002,0042f210
L"Hardware\\ResourceMap\\System Resources\\Physical Memory",0032f930)
ret=00403b17
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=00403b17
--- snip ---
Wineboot already creates a couple of hardware related registry keys:
Source:
http://source.winehq.org/git/wine.git/blob/7f9dfe273a80d31e3f8c5bd0c100c813…
Might be useful to add "Hardware\\ResourceMap\\System Resources" key here along
with actual physmem value.
Regards
--
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=41223
Bug ID: 41223
Summary: IDA MDI doesn't have scrollbars when it should
Product: Wine
Version: 1.9.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: b7.10110111(a)gmail.com
Distribution: ---
Created attachment 55488
--> https://bugs.winehq.org/attachment.cgi?id=55488
How it looks in Wine
To reproduce:
1. Launch IDA, have it maximized
2. Open a file, so that IDA begins analysis
3. Unmaximize main window
4. See lack of scrollbars in the MDI, despite child windows being too large to
fit.
5. Compare the same with Windows and see that there it does have the
scrollbars.
The only thing I get in the console is this:
fixme:win:LockWindowUpdate (0x500c4), partial stub!
fixme:win:LockWindowUpdate ((nil)), partial stub!
fixme:win:LockWindowUpdate (0x500c4), partial stub!
fixme:win:LockWindowUpdate ((nil)), partial stub!
--
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=32515
Bug #: 32515
Summary: Warhammer 40,000: Space Marine (Steam) fails to start
Product: Wine
Version: 1.5.20
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Classification: Unclassified
Created attachment 42894
--> http://bugs.winehq.org/attachment.cgi?id=42894
plain terminal output
On startup the game shows a black screen for a few seconds and audio from the
intro video can be heard for 0.5-1 second, then the game's own bug reporting
tool (Bugsplat) is popping up: "A problem has been encountered and the program
needs to close". No backtrace from Wine is generated.
A demo version is available on Steam, but I couldn't test it as I have the full
version.
http://store.steampowered.com/app/55150/
Steam installs MSVC++ 2005 runtime libraries and various DirectX components the
first time you start the game. Disabling gameoverlayrenderer in winecfg doesn't
help. I tested this bug with Wine 1.2.3, 1.4.1, 1.5.20.
Fedora 17 x86
Nvidia 250 / driver 304.64
X.Org X Server 1.12.4
Alsa 1.0.26
--
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.