http://bugs.winehq.org/show_bug.cgi?id=20530
Summary: SolidWorks Explorer 2010: Fails to start
Product: Wine
Version: 1.1.32
Platform: PC
URL: http://www.solidworks.com/sw/support/downloads.htm
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lukasz.wojnilowicz(a)gmail.com
Created an attachment (id=24467)
--> (http://bugs.winehq.org/attachment.cgi?id=24467)
Image of two warning windows
I'm using Wine wine-1.1.32-260-gf222a16 compiled on gcc (GCC) 4.4.1 20090725
(Red Hat 4.4.1-2) on Fedora 11 i386.
Steps to reproduce:
1) clean ~/.wine
2) install SolidWorks Explorer 2010 (swexplorer.exe) downloaded from URL given
in
heading
3) winetricks vcrun2005
4) launch "~/.wine/drive_c/Program Files/SolidWorks/SolidWorks Explorer
2010/solidworksexplorer.exe"
5) two warning windows appear and at the end graphical crash dialog
Result:
Application doesn't start
Expectation:
Application starts
--
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=20039
Summary: COM-port CTS/DSR lines stay low
Product: Wine
Version: 1.1.29
Platform: PC
URL: http://www.n1mm.com
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rx9tx(a)qrz.ru
CC: rx9tx(a)qrz.ru
Program installation http://www.pi4dec.nl/n1mm/N1MM-FullInstaller.exe
Latest update http://www.pi4dec.nl/n1mm/N1MM-newexeV9.9.3.exe
Program communicates with the radio through an interface based on USB->COM
converter on FTDI chip. After the com port initialisation the CTS/DSR lines
stay low, problem is that radio can not read the data if they are low.
When running the program under Windows, COM-port initialisation sets the
CTS/DSR lines in the high state.
Is there any way to set them high?
--
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=49121
Bug ID: 49121
Summary: Themida Demo 2.4.5.0 crashes on start
Product: Wine
Version: 5.2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
The program can't be started, because it crashes directly on start.
--
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=37617
Bug ID: 37617
Summary: QQIntl will crash after log in
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hillwoodroc(a)gmail.com
Distribution: ---
Created attachment 50065
--> https://bugs.winehq.org/attachment.cgi?id=50065
QQIntl log
1.Download from http://dldir1.qq.com/qqfile/QQIntl/QQi_PC/QQIntl2.11.exe
2.winetrick riched20 msctf.
3. login with the folloing testing account:
account: 1469264807
Password: winedebug
4.QQIntl will crash.
It seems that we can usr winetrick wininet to fix.
--
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=26548
Summary: GomezPEER is always visible behind other windows
Product: Wine
Version: 1.3.16
Platform: x86-64
URL: http://lastmile.gomez.com/PEERInstall.exe
OS/Version: Linux
Status: NEW
Keywords: download, integration
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
Created an attachment (id=33811)
--> (http://bugs.winehq.org/attachment.cgi?id=33811)
Screenshot: console is on top but Gomez still visible
To be a bit more accurate, GomezPEER can be seen behind other windows, when
GomezPEER updates its window. Parts of the window updates every second so it
is effectively always there.
This is not a new problem, it has existed for as long as I can remember.
Currently using Gnome/Ubuntu/GDM/fglrx but appears on all desktops I have used.
Desktop effects are disabled and windows are not transparent.
The attached screenshot should make it obvious.
--
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=20628
Summary: chromium's ipc_tests.exe's IPCChannelTest.ChannelTest
fails occasionally
Product: Wine
Version: 1.1.32
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
On Wine, but not on Windows, the command
wine src/chrome/Debug/ipc_tests.exe --gtest_filter=IPCChannelTest.ChannelTest
fails about 5% of the time. (You may need to run it several hundred
times to see the first failures.)
Sadly, with +relay it never fails.
Related source:
http://src.chromium.org/viewvc/chrome/trunk/src/ipc/ipc_tests.cchttp://src.chromium.org/viewvc/chrome/trunk/src/ipc/ipc_channel_win.cc
To repeat:
$ wget http://kegel.com/wine/chromium/chromium-tests.tar.bz2
$ tar -xjvf chromium-tests.tar.bz2
$ while true
do
wine src/chrome/Debug/ipc_tests.exe --gtest_filter=IPCChannelTest.ChannelTest
> log 2>&1
grep FAILED log && break
done
--
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=11667
Summary: Window contents not updated properly after being moved
Product: Wine
Version: 0.9.55.
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Hi,
I believe this bug relates to DirectDraw. (Apologies for my lack of detailed
knowledge about Windows.)
In some cases, moving a window whose contents are updated by DirectX calls
causes trash/garbage to appear when the window is drawn in its new position,
My theory is that WINE remembers the window contents at the moment the user
begins dragging the title bar, and simply copies that to the new window
position. If the program continues to update the DirectX buffer while the user
is moving the window frame, WINE puts the old/stale buffer contents in the
moved window. This happens in both normal and virtual desktop modes.
For applications like video players, this effect may not be very noticeable if
the player redraws the whole window every frame. But for applications which
don't do that, the effect can be quite ugly.
One program I have found which shows this problem is WinUAE. To reproduce:
- Download and install WinUAE from http://www.winuae.net/
- Download an example disk image for testing, e.g.
ftp://ftp.coresystems.de/pub/uae/rsi1.adf.gz
- Start WinUAE and select the rsi1.adf.gz file for emulated drive DF0:, and
start the emulation.
- Once the demo graphics appear, repeatedly move the main WinUAE window and
notice the problem.
--
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=44317
Bug ID: 44317
Summary: 3.0-rc5 removes elements displayed in version 2.18,
displays hidden instead.
Product: Wine
Version: 3.0-rc5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: brian.black(a)email.com
Distribution: ---
Created attachment 60167
--> https://bugs.winehq.org/attachment.cgi?id=60167
Example image 01 2.18 staging comparison
Mounts, eyes, external layers of armor fails to render. (Invisible) bounding
boxes are displayed as opaque black or red boxes at campfires. Unlike 2.18
staging 3.0-rc5 is missing elements rendered in 2.18 such as tree leaves and
other background elements.
I will now illustrate this with the attachments. While I edited these using
GIMP to add text and call outs, no graphic details to images were altered.
1. Image01 (2.18) shows my "pet" flying on the left side of the screen wearing
his orange clothing, the buildings in the background are fogged in blue as they
should be, and the big tree has the pinkish leaves. All of these elements are
normal and have no issue. My character is missing his boots (no feet) and has
no eyes, while all other character have all these items.
2. Image02 (3.0-rc5) shows my "pet" now flying in front of the tree on the
right. The tree is missing leaves and is now bare. The background is now black
and even more elements are missing from my character than before.
3. Image03 (3.0-rc5) shows me mounted on my wolf the same mount as my friend
posed nearby to illustrate the effect is just my character and not other
characters. The application it seems handles the individual character
differently than those of other players and non player AIs.
This game is completely unplayable under 3.0-rc5, due to the fact many areas
show as solid colors (such as black). Making it near next to impossible to
navigate dungeons. Anyone playing in 2.18-staging should remain there for game
play purposes. While debugging continues in 3.0 and beyond.
--
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=32290
Bug #: 32290
Summary: SSF v0.12 Beta R3 cannot be run properly
Product: Wine
Version: unspecified
Platform: x86-64
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: radiowavers(a)gmail.com
Classification: Unclassified
Software information:
--------------------------------------------------------------------------------------
http://en.wikipedia.org/wiki/SSF_(emulator)http://www7a.biglobe.ne.jp/~phantasy/ssf/index.htmlhttp://www7a.biglobe.ne.jp/~phantasy/ssf/files/SSF_012_beta_R3.zip
--------------------------------------------------------------------------------------
System information:
--------------------------------------------------------------------------------------
OS version: Mac OS X Mountain Lion 10.8.2
X Window System: XQuartz 2.7.4 (xorg-server 1.13.0)
Wine version: 1.5.18 - latest development version, built with GCC 4.7.2 from
sources.
I am using development version, because it has the built-in fix for Bug 32101.
All the dependencies of Wine and GCC are the latest stable.
--------------------------------------------------------------------------------------
First of all, bug 12622 needs to be reopened (or a new version of it to be
created, since
"fixme:win:EnumDisplayDevicesW ((null),0,0xRandomMemoryAddress,0x00000000),
stub!" error is not fixed by inserting/mounting a CD!
If I mount/insert a CD, I get this console error anyway, and program closes in
two seconds!
If I don't mount/insert a CD, I get this console error and the program launches
with warning message "?????CD??????????"
(no CD present). But, if I ignore this warning message and don't click OK
(which would result in program termination)
I could navigate in the main program window between menu options (with keyboard
arrows only, since program window
doesn't expand and anything except "File(F)" is not visible. I click "File(F)"
and then left/right keyboard arrows)
However, if I click "Option (O)", "Rotation", "Window Size", "Sound Record
(S)", "Video Record (V)",
or even "cep(C)" (which should show a small message, like "About...") I get a
"Program Error" message.
In the attachment, you could see a .zip archive with all the different
backtraces I got for these options.
--
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=47217
Bug ID: 47217
Summary: Adobe Lightroom crashes in
d2d:d2d_device_context_DrawImage
Product: Wine
Version: 4.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: bugs(a)bzatek.net
Distribution: ---
Created attachment 64488
--> https://bugs.winehq.org/attachment.cgi?id=64488
gzipped console log
When the GPU Acceleration is switched on in the Lightroom configuration,
opening Import module crashes wine. This bug has been sitting there for some
time, spanning from Lightroom releases 7.2, 7.5 and 8.1 (all 64b) and wine
releases back to 3.20 AFAIR. Switching the GPU Acceleration off makes the
Import module work as expected (albeit slow).
Not exactly sure this is a D2D issue, the traces usually look like this:
> 0029:fixme:d2d:d2d_device_context_CreateEffect iface 0x401aa400, effect_id {1feb6d69-2fe6-4ac9-8c58-1d7f93e7a6a5}, effect 0x23e1e0 stub!
> 0029:fixme:d2d:d2d_effect_SetInput iface 0x7ff01d4c8780, index 0, input 0x7ff03fb35380, invalidate 1 stub!
> 0029:fixme:d2d:d2d_effect_SetValue iface 0x7ff01d4c8780, index 2, type 0, value 0x23e370, value_size 4 stub!
> 0029:fixme:d2d:d2d_effect_SetValue iface 0x7ff01d4c8780, index 0, type 0, value 0x23e370, value_size 4 stub!
> 0029:fixme:d2d:d2d_effect_GetOutput iface 0x7ff01d4c8780, output 0x23e370 stub!
> 0029:fixme:d2d:d2d_device_context_DrawImage iface 0x401aa400, image (nil), target_offset {2.66799965e+01, 1.46500000e+02}, image_rect (null), interpolation_mode 0x1, composite_mode 0 stub!
> wine: Unhandled page fault on read access to 0x00000000 at address 0x572ebed (thread 0029), starting debugger...
Let me know in case any other information is 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.