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=47453
Bug ID: 47453
Summary: Running setup for Xerox GlobalView, gets error, gives
backtrace.txt file
Product: Wine
Version: 4.0.1
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aa271828(a)earthlink.net
Created attachment 64815
--> https://bugs.winehq.org/attachment.cgi?id=64815
this was generated upon setup
Running setup for Xerox GlobalView, gets error, gives backtrace.txt file.
This is from 1996 and it runs on win 3.1, 95 & 98.
It's a 16 bit application.
I was in win 95 mode when I got the error on setup.
Here's where I got it;
https://winworldpc.com/product/xerox-globalview/21-for-windowshttp://toastytech.com/guis/gv.html, for description
--
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=6194
yother.andrew(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yother.andrew(a)gmail.com
--- Comment #30 from yother.andrew(a)gmail.com ---
Do you have a installer that I can run to test with the latest version of Wine?
--
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=230
tomplatz <tomplatz567(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tomplatz567(a)gmail.com
--- Comment #18 from tomplatz <tomplatz567(a)gmail.com> ---
Created attachment 64885
--> https://bugs.winehq.org/attachment.cgi?id=64885
132
--
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=47488
Bug ID: 47488
Summary: Keyboard insertion point interference when running
Wine app
Product: Wine
Version: 4.0.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: scw189(a)cox.net
Distribution: ---
When running a Wine app (Legacy9, genealogy program) in the background and then
trying to type anything with a word processor or do a Google search, it is
difficult to enter text because the insertion point character keeps
disappearing after 2-5 second. Then you have to click again in the text field
to reset the insertion point and try to type a few characters before it
disappears again. This issue stops as soon as the Wine application is
terminated. Mouse operation does not seem to be affected, just keyboard
character input is impaired because the insertion point is continually being
lost.
Cannot find any messages or error codes being asserted and system does not
'crash'.
OS is Linux Mint 19.1 Cinnamon with all updates applied. Computer is Dell
Dimension E521 with 64bit dual core Athlon CPU, 6gb memory.
--
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=5977
Lewis Cowles <lewiscowles(a)me.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lewiscowles(a)me.com
--- Comment #32 from Lewis Cowles <lewiscowles(a)me.com> ---
To Echo what winetest@luukku said, I adjusted the resolution to 800x600x32 in
Armada, which led to seeing some the texture for the animation When hovering.
This is absolutely an issue with draw order, but enabling "fixes" I assumed
would counter this, did nothing useful, and in-fact made the game unusable.
Debian 10 buster, winetricks, wine 1386, Quicktime 3 & DX from armada installer
installed, directplay activated, virtual desktop forced to 1024x768 (game seems
to ignore & go fullscreen)
Also needs to be launched from launcher. Game won't run by itself. Odd
--
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.