https://bugs.winehq.org/show_bug.cgi?id=45036
Bug ID: 45036
Summary: Cisco Jabber 11.x crashes on unimplemented function
IPHLPAPI.DLL.GetIpNetTable2
Product: Wine
Version: 3.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: iphlpapi
Assignee: wine-bugs(a)winehq.org
Reporter: paul(a)lemmons.name
Distribution: ---
Created attachment 61159
--> https://bugs.winehq.org/attachment.cgi?id=61159
Console log of failure
wine: Call from 0x7bc51389 to unimplemented function
IPHLPAPI.DLL.GetIpNetTable2, aborting
When attempting to start the Cisco Jabber client
wine: 3.6 Build 527 - Development 448344c5e4 (Apr 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=37334
Bug ID: 37334
Summary: Cisco Jabber fails to run
Product: Wine
Version: 1.7.27
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: daniel.masur(a)idealo.de
Created attachment 49647
--> https://bugs.winehq.org/attachment.cgi?id=49647
Console output upon running CiscoJabber.exe
Hi.
As a normal user, after installing ie7 into a fresh .wine folder using:
WINEARCH='win32' winetricks ie7
copying ksuser.dll into system32
and then installing the Cisco Jabber Client using:
WINEARCH='win32' wine msiexec /i CiscoJabberSetup.msi
I get the attached console output when running the following:
bash -c "LC_MESSAGES=C WINEARCH='win32' wine .wine/drive_c/Program\
Files/Cisco\ Systems/Cisco\ Jabber/CiscoJabber.exe"
bash -c "LC_MESSAGES=C ..." for englishifying the console output.
--
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=44922
Bug ID: 44922
Summary: Cisco Jabber 11.x crashes on unimplemented function
IPHLPAPI.DLL.GetIpForwardTable2,
Product: Wine
Version: 3.5
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: iphlpapi
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
extracted from bug 37228 (https://bugs.winehq.org/show_bug.cgi?id=37228#c21)
--- snip ---
$ env WINEPREFIX="/home/xxxxxx/.wine32" wine 'C:\Program Files\Cisco
Systems\Cisco Jabber\CiscoJabber.exe'
...
0009:fixme:shcore:GetDpiForMonitor (0x1, 0, 0x32ef48, 0x32ef44): semi-stub
0009:fixme:netapi32:DsGetDcNameW ((null), (null), (null), (null), 40000000,
0x96ad1dc): stub
0009:fixme:ntdsapi:DsBindW ((null),(null), 0x96ad1d8): stub!
0009:fixme:ntdsapi:DsCrackNamesW : stub
wine: Call from 0x7bc51289 to unimplemented function
IPHLPAPI.DLL.GetIpForwardTable2, aborting
....
--- snip ---
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=37228
Bug ID: 37228
Summary: Cisco Jabber will not run
Product: Wine
Version: 1.7.25
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: davidc502(a)tds.net
Created attachment 49501
--> https://bugs.winehq.org/attachment.cgi?id=49501
Errors when trying to run Jabber through console.
Cisco Jabber does not run after install. A grey screen pops up, but shortly
after am requested to close unresponsive application.
URL to the ciscoJabberSetup.msi ->
http://personalpages.tds.net/~davidc502/Jabber/
See attached for Errors whilst trying to run Jabber in Console window.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=10522
Summary: endless WM_PAINT loop bug (update regions, queue paint
count)
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://www.microsoft.com/whdc/devtools/debugging/install
x86.mspx
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-user
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Created an attachment (id=9265)
--> (http://bugs.winehq.org/attachment.cgi?id=9265)
trace with WINEDEBUG=+tid,+message,+win,+server
Hello,
I've seen this bug a while ago in other apps but ignored it because it was not
easily to reproduce.
Well until recently when I tested some stuff with windbg from "Debugging Tools
for Windows" (Microsoft).
I used debugging tools version 6.8.4.0 and recent GIT
(wine-0.9.49-302-g58b85bb).
Immediately when a child window was opened using toolbar (register, locals, ..
whatever), windbg would become unresponsive, eating most CPU.
Happens in both GUI modes - "floating/docking toolwindow" and "MDI emulation.
Though "MDI emulation" is more obvious, it actually shows the endless
refreshing (window caption).
Attached is WINEDEBUG=+tid,+message,+win,+server log.
Additionally I added a trace message which prints the current queue paint count
(when incremented or fetched) which makes some things easier to spot.
Printed as "inc_queue_paint_count: %d" and "get_message_paint_count: %d".
The window hierarchy is as follows:
--- snip ---
*root*=0x10020
Shell_TrayWnd=0x10022
WinDbgFrameClass=0x10024
DockClass=0x10026
ToolbarWindow32=0x10028
msctls_statusbar32=0x1002a
tooltips_class32=0x1002e
WinBaseClass=0x10030
ToolbarWindow32=0x10032
SysListView32=0x10034
SysHeader32=0x10036
RichEdit20W=0x10038
--- snip ---
After the child windows are created the queue paint count never drops to zero,
resulting in endless WM_PAINT processing.
Maybe some update (region) code path missed or flags problem?
I played a bit with ignoring null region updates and it seemed to help a bit
(preventing endless WM_PAINT loop) though other stuff wasn't drawn properly
then.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42222
Bug ID: 42222
Summary: BCG Month/Year list goes behind date control.
Product: Wine
Version: 2.0-rc5
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
Created attachment 56862
--> https://bugs.winehq.org/attachment.cgi?id=56862
Show the control behind the Month picker
Run BCGPControls.exe
Select Time Controls on the left hand side.
In CBCGDataTimeCtrl the group
Use the dropdown arrow to show a Date picker.
Click on the Month/Year header this popup.
The Month/year List now appears behind the Calender.
--
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=31874
Bug #: 31874
Summary: this program crash when changing the UI style
Product: Wine
Version: 1.5.14
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jactry92(a)gmail.com
Classification: Unclassified
Created attachment 41947
--> http://bugs.winehq.org/attachment.cgi?id=41947
'backtrace.txt' is log produced by wine
I used wine 1.5.14 in Ubuntu 12.04.1 32bit to run this
program('client.exe'):http://222.200.98.151/ubuntu/Downloads/client.tar.gz
And it crash when I try to change the UI style(client the button which was
marked by a red circle in the picture in attachment)
After it crach you can't run it again.In order to reappear it, you can change
the value of 'HKEY_CURRENT_USER/Software/ChinaGDS/S2000/JySvr1/UI' to '0'.
'backtrace.txt' is log produced by wine
This is output information in console:
$ wine client.exe
fixme:wbemprox:client_security_SetBlanket 0x442fcd80, 0x13dd68, 10, 0, (null),
3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0x442fcd80
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x328ed8,0x328edc): stub
wine: Unhandled page fault on read access to 0x00000020 at address 0x4b0b0f
(thread 0025), starting debugger...
--
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.