http://bugs.winehq.org/show_bug.cgi?id=9802
Summary: ImageReady CS2 crashes on startup
Product: Wine
Version: 0.9.44.
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-gui
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mikolaj.zalewski(a)gmail.com
There is a C++ exception after receiving a WM_MOUSEACTIVATE and then after a
call to PeekMessageW there is a access violation exception. The C++ exception
seems to be the main cause but it's hard if it is and why it is thrown.
--
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=46462
Bug ID: 46462
Summary: Drop fps
Product: Wine
Version: 4.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mietkong(a)gmail.com
Distribution: ---
Hi When im playing elder scrolls oblivion fps drops down to 5-10 fps only when
i moving mouse . If mouse is not moving fps is high how to solve this
--
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=34995
Bug #: 34995
Summary: Crashes in Wineskin
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cycle898(a)yahoo.com
Classification: Unclassified
Created attachment 46632
--> http://bugs.winehq.org/attachment.cgi?id=46632
Backtrace/Error Log
Wineskin 2.5.12 : crashes during certain parts of games with what could be
considered moderate to high graphical output. This happens several times over
various playthroughs. This error occurs at random intervals.
--
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=45544
Bug ID: 45544
Summary: Dialog messages pop under instead of popping up in
RadiAnt DICOM Viewer
Product: Wine
Version: 3.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bozkar(a)gmail.com
Distribution: Debian
Most of the dialog boxes pops under the main window in RadiAnt DICOM Viewer -
they occasionally pops up correctly.
Tested with PACS download dialog box, keyboard shortcuts settings dialog box,
about box.
They blink for a second and then they go under the main window.
Occasionally the program behaves correctly.
How could I help here?
--
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=45545
Bug ID: 45545
Summary: CUDA acceleration much slower then in Windows 10 in
RadiAnt Viewer on the same hardware
Product: Wine
Version: 3.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: nvcuda
Assignee: wine-bugs(a)winehq.org
Reporter: bozkar(a)gmail.com
Distribution: Debian
RadiAnt Viewer now supports nvcuda.dll acceleration in 3D MPR / VR
reconstruction, but it's pointless to actually use it - on my box, GTX 970 it
is much slower then in Windows 10 (and slower then in CPU).
It is new, not yet optimized feature, but the difference in speed (subjective
FPS score) on the same hardware looks significant.
--
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=41859
Bug ID: 41859
Summary: pingo crashes when optimizing PNG images
Product: Wine
Version: 1.9.24
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: danielbermond(a)yahoo.com
Distribution: ---
Created attachment 56266
--> https://bugs.winehq.org/attachment.cgi?id=56266
pingo wine terminal log when using PNG image
With JPG image: works well.
With PNG image: it just crashes. Tested with all possible pingo options.
Without command line arguments: shows the help screen as usual.
pingo is a command line PNG/JPG image optimizer that is shipped as a single
'.exe' without needing installation.
Tested with the 3 methods of running Console User Interface programs: 'wine',
'wineconsole --backend=user' and 'wineconsole --backend=curses'. All of them
crashes when using PNG image.
Website: http://css-ig.net/pingo
Download: http://css-ig.net/tools/pingo.zip
OS: Arch Linux x86_64
Wine: 1.9.24 (with all optional dependencies installed)
pingo: 0.41
--
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=46108
Bug ID: 46108
Summary: Wine creates env var with empty string for name and it
breaks python-pip
Product: Wine
Version: 3.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stu.axon(a)gmail.com
Distribution: ---
When I try and install things using pip (from python 2.7, since python 3.5
install doesn't work right not).
it fails, with
*** ValueError: illegal environment variable name
If I open the python interpreter I can see there is an env var with the name of
an empty string:
>>> import os
>>> os.environ['']
'Z:=Z:\\home\\stu\\Downloads'
I had a look at this outside of wine and the env var doesn't show up when
running the same python.
I edited pythons pip code to remove the env var:
~/.wine/drive_c/Python27/Lib/site-packages/pip/_internal/utils/misc.py
I changed these lines:
env = os.environ.copy()
if extra_environ:
env.update(extra_environ)
To:
env = os.environ.copy()
if extra_environ:
env.update(extra_environ)
env.pop('')
And then pip succeeds
--
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=46832
Bug ID: 46832
Summary: Drag and drop of multiple files
Product: Wine
Version: 4.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: k8auf1947(a)cometchaser.de
Distribution: ---
Created attachment 63865
--> https://bugs.winehq.org/attachment.cgi?id=63865
Screenshot how to find the function used to drag and drop
Hi,
Drag and drop of multiple fit - files in the commercial application Astroart
6.0 doesn't work as in Windows.
I attached a screenshot. Drag and drop can also be made with jpg files. I
normally use it with fit files.
Astroart: http://www.msb-astroart.com/
I can provide the Setup file.
--
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=46170
Bug ID: 46170
Summary: Programs that get MIDI data from the "Midi Through"
port will crash
Product: Wine
Version: 3.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: realnc(a)gmail.com
Distribution: ---
Created attachment 62822
--> https://bugs.winehq.org/attachment.cgi?id=62822
Example MIDI file that reproduces the crash.
Any Windows software that is configured to use the ALSA "Midi Through" port for
MIDI input (as provided by the snd-seq-dummy kernel module) will crash with a
page fault exception dialog. This only happens with certain MIDI data. It seems
to depend on the speed of the MIDI data.
The issue was originally discovered by using the Linux version of ScummVM
together with the Windows program "Falcosoft Midiplayer" as a means of using a
Windows-only VSTi as a software MIDI synth for ScummVM. In such a setup, the
Linux program is configured to use the "Midi Through" port as MIDI-out, and the
Windows program is configured to use it as MIDI-in.
However, after capturing the specific MIDI data that triggers the crash into a
*.mid file, playing that file in any MIDI player that uses "Midi Through" for
MIDI-out and *any* Windows MIDI program that uses "Midi Through" as MIDI-in,
will crash the Windows program.
The problem is reproducible by at least two people on two different machines.
It is reproducible by building current Wine Git master, without any third-party
patches, and on a cleared ~/.wine directory. Example steps to reproduce this
are:
1. Make sure the "Midi Through" port is available. aplaymidi -l should list
something like:
$ aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
"Midi Through" is port 14:0 here. If no such port exists, load the
"snd-seq-dummy" kernel module:
$ modprobe snd-seq-dummy
2. Download the attached "crash.mid" file.
3. Download the Falcosoft Midiplayer from:
http://falcosoft.hu/softwares.html#midiplayer
4. Run MidiPlayer.exe in Wine and click the gear icon to open the settings.
Check the "Use Bass (Soundfonts/VSTi)" checkbox (this is only necessary in
order to avoid an unrelated Wine crash.) In the "Midi In" group, check the
"Active" checkbox. In the "Input Port" drop-down selection list, select "Midi
Through Port-0". Click OK.
5. Play the "crash.mid" file using a Linux MIDI player, like aplaymidi, telling
it to use the Midi Through port as output:
$ aplaymidi -p 14 crash.mid
Substitute "14" with the actual port if it differs on your system. It might
take a few attempts before the crash occurs. Here, it crashes about 80% of the
time.
The above steps are just an example. The crash is reproducible with any other
Windows MIDI client, not just the Falcosoft one. See:
https://www.vogons.org/viewtopic.php?f=24&t=48207&start=760#p714667
--
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.