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.
https://bugs.winehq.org/show_bug.cgi?id=47160
Bug ID: 47160
Summary: wine-staging is unable to execute executable which is
soft link in linux.
Product: Wine-staging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: l12436(a)yahoo.com.tw
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Since recently wine-staging version, wine-staging is no longer able to
successful recognize soft link directory or executable.
I have many directory is soft link to save disk space.
I can not found which patch cause this issue.
--
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=47319
Bug ID: 47319
Summary: Wine 4.9 does not dereference symlinks
Product: Wine-staging
Version: 4.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kanakkshetri(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
I have a symbolic link ~/Audio/hello.flac that is pointing
/mnt/audio/hello.flac . I have also set ~/Audio to be Y: in wine.
Prior to the 4.9 release, windows applications, such as Wine File Manager or
foobar2000 version 1.4.4 ( http://foobar2000.org) would dereference that
symlink and see that it is a 30Mb file that is a valid flac audio file.
With 4.9, file manager shows the size as 0 and foobar2000 cannot read the file
at all. I am on Fedora 30, where a dnf downgrade took me back to 4.5-1, where
this works as expected.
I have verified this on two different machines, using Wine File Manager as well
as foobar2000. I have also seen the same behavior in Fedora 29 (with Wine 4.9),
so I don't think it is OS specific.
Additional context:
- my data is on an XFS file system
- the symlinks are present because the data is managed by git annex (
https://git-annex.branchable.com/ )
- However, i can repro the problem without involving git annex merely by
creating symlinks.
Please let me know if there is any additional details I can provide or
experiments I can run locally. Thank you for the great work on 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=47346
Bug ID: 47346
Summary: [Epic Games Launcher]Crashes when Winecfg is set to
Win10
Product: Wine-staging
Version: 4.9
Hardware: x86
URL: https://epicgames-download1.akamaized.net/Builds/Unrea
lEngineLauncher/Installers/Win32/EpicInstaller-9.13.0.
msi?launcherfilename=EpicInstaller-9.13.0.msi
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: Gentoo
Hello,
Bug easy to reproduce :
1- Download EGS
2- Install Arial fonts with winetricks
3- Install EGS and wait the update crash.
4- Launch EGS with "-SkipBuildPatchPrereq -opengl" arguments + Win7/Win8/Win8.1
= works
5- Launch EGS with "-SkipBuildPatchPrereq -opengl" arguments + Win10 = crashes
With Win7 and/or Win10, the login screen works correctly, it's the launcher
itself which does not work with Win10, see screenshots attachment. I added
output log for Win7 + Win10 too.
--
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=47273
Bug ID: 47273
Summary: Unix symlinks no longer work in wine-staging 4.8
Product: Wine-staging
Version: 4.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Keywords: regression
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gabrielopcode(a)gmail.com
CC: erich.e.hoover(a)gmail.com, leslie_alistair(a)hotmail.com,
z.figura12(a)gmail.com
Distribution: ---
With wine-staging-4.8, symlinks created on Linux (i.e. outside of Wine) to
directories no longer work in Wine. They show up as empty files. Previously,
and on wine-devel, they work just fine and even show up as symlinks under file
managers.
The culprit seems to be the updated ntdll-Junction_Points patchset, though I've
no idea what part of it specifically does this.
I know that support for NT symlinks and junctions was updated to differentiate
them, but IMO support for native unix symlinks should remain as it was before
this updated patchset, so they continue to work like before. Many people,
including me, rely on that for our workflow.
Unfortunately I don't know how to bisect wine-staging patches so I can't
pinpoint exactly which patch in the series is responsible for this regression.
--
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=47426
Bug ID: 47426
Summary: The sims 4 games crashes and freezes
Product: Wine
Version: unspecified
Hardware: Other
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: apphelp
Assignee: wine-bugs(a)winehq.org
Reporter: giseeelle58(a)gmail.com
Created attachment 64774
--> https://bugs.winehq.org/attachment.cgi?id=64774
report of crash
The Sims 4 game crashes and freezes every 10 minutes
--
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.