https://bugs.winehq.org/show_bug.cgi?id=52793
Bug ID: 52793
Summary: commit c7e87b536edb28bb48162690e0d42c9ba9ccb43c breaks
Total Commander internal file associations
Product: Wine
Version: 7.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: felix.huber(a)schyf.de
Distribution: ---
Calling native Linux applications with internal associations by using a script
with the line:
/usr/bin/xdg-open "`wine winepath -u "$1"`"
works only when output of stderr can be printed to a console.
Redirecting stderr to /dev/null breaks this mechanism starting with commit
c7e87b536edb28bb48162690e0d42c9ba9ccb43c: the script does not get called
anymore.
--
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=52789
Bug ID: 52789
Summary: Unwanted Console Creation when Winegcc compiled
Processes are started
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: chopinbig(a)tutanota.com
Distribution: ---
When winegcc apps are run, a console (terminal) pops up with Wine 7.5 which
didn't happen in Wine 7.4 or any previous Wine version either.
This is odd behaviour.
If the unwanted console window is closed, then it causes a crash.
I think I've tracked it down to these commit's
https://source.winehq.org/git/wine.git/commit/7b65ef3afbe880b82e89656435261…https://source.winehq.org/git/wine.git/commit/c7e87b536edb28bb48162690e0d42…https://source.winehq.org/git/wine.git/commit/f034084d49b354811096524d472ae…
2022-03-17 Eric Pouech kernelbase: Handle corner case in CreateProcess.
commit | commitdiff | tree
2022-03-17 Eric Pouech start: Force no console creation when using start
... commit | commitdiff | tree
2022-03-17 Eric Pouech services: Start services detached from console.
commit | commitdiff | tree
--
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=52786
Bug ID: 52786
Summary: "wine cmd.exe /c [any command which outputs text]"
returns zero length text
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: bill2allison(a)yahoo.co.uk
Distribution: ---
Works correctly only when executed from a terminal (xterm etc)
Fails when wine is invoked (directly or by another program such as winetricks)
from desktop menu or launcher or a .desktop file.
MY ENVIRONMENT
--------------
OpenSUSE Tumbleweed
KDE/Plasma
Wine 7.5
TO REPRODUCE
------------
1) From the desktop launcher run
wine cmd.exe /c echo 'hello' > ~/test.txt
Each time it is run, the test.txt timestamp is updated but the file remains
empty
2) From the desktop launcher run
winetricks --gui
Displays info then error message 'wine cmd.exe /c echo '%AppData%' returned
empty string, error message "" '
3) Issue test 1 above in xterm or similar then test.txt contains "hello"
4) Issue test 2 above in xterm or similar then winetricks starts and runs
normally
WORKAROUND
----------
Include terminal=true in affected .desktop files and menu configs or start
those programs from within a terminal
--
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=49111
Bug ID: 49111
Summary: ELWAVE Demo installer 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: ---
Created attachment 67087
--> https://bugs.winehq.org/attachment.cgi?id=67087
Wine log
The installer crashes as soon as its run, see attached log - that's a full log,
not only the backtrace.
--
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=52796
Bug ID: 52796
Summary: wine 7.5+ can no longer enqueue files from Dolphin to
foobar2000
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kohhnztqscldrekdqn(a)kvhrw.com
Distribution: ---
With wine 7.4 and earlier it was possible to select audio files in Dolphin and
send them to foobar2000's playlist with 'Open With > foobar2000' context menu
entry. With wine 7.5 and 7.6 foobar2000 will start but file selection doesn't
appear in the playlist. Drag & drop from Dolphin still works though.
Below foobar2000 launcher script and .desktop file are similar to what I use if
that matters.
https://aur.archlinux.org/cgit/aur.git/tree/foobar2000.sh?h=foobar2000https://aur.archlinux.org/cgit/aur.git/tree/foobar2000.desktop?h=foobar2000
--
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=52783
Bug ID: 52783
Summary: error: unknown type name ‘uint64_t’
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winealsa.drv
Assignee: wine-bugs(a)winehq.org
Reporter: version2013(a)protonmail.com
Distribution: ---
Created attachment 72164
--> https://bugs.winehq.org/attachment.cgi?id=72164
log.txt
Compiling in distro with:
compiler version 4.8.4
# gcc --version
glibc 2.19
# ldd --version
config line:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x
--libdir=/usr/lib32 CFLAGS="-O2 -march=i686 -mtune=i686"
Compile error in wine-7.5
In function ‘get_time_msec’:
error: ‘uint64_t’ undeclared (first use in this function)
warning: control reaches end of non-void function [-Wreturn-type]
--
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=49112
Bug ID: 49112
Summary: ELWAVE doesn't start - detects Wine as VM
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 doesn't start, since it refuses to work in a VM but detects Wine as
such.
Seems to work on older CPUs though, so maybe that's a clue.
Reported in the forums: https://forum.winehq.org/viewtopic.php?f=2&t=33826
--
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=51387
Bug ID: 51387
Summary: Critical Section timeout between
"dlls/user32/user_main.c: user_section" and
"dlls/winex11.drv/window.c: win_data_section"
Product: Wine
Version: 4.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: l.arzeni(a)iname.com
Distribution: ---
Created attachment 70242
--> https://bugs.winehq.org/attachment.cgi?id=70242
application logs
Environment: GNU Debian Linux, kernel 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1
(2021-03-19), Wine 4.0.2, but I tested it and I can reproduce the issue under
every release of wine32, from release 1.5 to release 5.0.3,
I'm running an old windows application. It works showing a list of records from
an ODBC connection, then when a record is clicked, it opens a form for editing
the record. It's similar to MS Access, but the application is written in a 4GL
db language called clarion. I can share the sources, if needed.
The application works fine under "native" windows (tested in all releases of
windows, from windows XP to Windows 10).
The application looks fine, but hangs after a while, if I run it under wine:
env WINEPREFIX=/home/user1/.wine32 wine /srv/data/shared/LicenseManager.exe
The log shows that there is a timeout in a critical section, may be a deadlock
between:
"dlls/user32/user_main.c: user_section"
and
"dlls/winex11.drv/window.c: win_data_section"
This is the relevant lines of the logs:
0024:err:ntdll:RtlpWaitForCriticalSection section 6EDB7C80
"dlls/user32/user_main.c: user_section" wait timed out in thread 0024, blocked
by 0114, retrying (60 sec)
0114:err:ntdll:RtlpWaitForCriticalSection section 7DB04220
"dlls/winex11.drv/window.c: win_data_section" wait timed out in thread 0114,
blocked by 0024, retrying (60 sec)
To solve the issue, I run it with "taskset --cpu-list 0 ", that is:
env WINEPREFIX=/home/user1/.wine32 taskset --cpu-list 0 wine
/srv/data/shared/LicenseManager.exe
But, if I user the taskset, the application GUI artifacts became "dirty" , and
I need to close and reopen the window to redraw them properly.
Is there any clue to solve this issue, or, at least, to avoid the garbage on
the user interface when running under the "taskset" command?
Please note: the issue is not "application specific" but, afaik, instead the
bug affects all application generated with "clarion"
Regards, Luca
--
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=52846
Bug ID: 52846
Summary: Capture One 22 fails to start with wbemprox related
crashes
Product: Wine
Version: 7.6
Hardware: x86-64
URL: https://www.captureone.com/en/new-update/capture-one-2
2
OS: Linux
Status: NEW
Keywords: dotnet, download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Created attachment 72244
--> https://bugs.winehq.org/attachment.cgi?id=72244
+wbemprox,+mountmgr,+seh
Hi, a user reported trouble with this program on the forum so i gave it a try.
Apparently for him it crashed inside wbemprox, but the crash is for me
different, and more unfortunate it differs from time to time, and every now and
then it does`t crash at all but just starts.... But all crashes look similar
like: System.AccessViolationException: Attempted to read or write protected
memory. This is often an indication that other memory is corrupt.
at
System.Management.SecuredIEnumWbemClassObjectHandler.Clone_(IEnumWbemClassObject&
ppEnum)
at System.Management.ManagementObjectCollection.GetEnumerator()
I attached one of the crashes to this report (+seh,+wbemprox,+mountmgr).
One thing that can be seen it queries for property "Characteristics" from
win32_processor, that is afaics missing, but that is probably not the cause of
the crashes; to rule that out could it be added?
It might be due to mountmgr.sys insufficiencies, but i cannot tell really for
sure.
Anyway, one way to reliably get the program started 100% is disabling
mountmgr.sys and/or wbmprox...
(Note: I installed native dotnet48, d3dcompiler_47 and arial via winetricks)
--
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=52508
Bug ID: 52508
Summary: EnumDisplayDevices() fails in obscure ways on 32-bit
arch when 64-bit Vulkan is present but 32-bit is
missing
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
CC: jacek(a)codeweavers.com, zzhang(a)codeweavers.com
Distribution: ---
FWIW, this is easy to trigger by running 32-bit ddraw:ddraw1.
I'm fine with calling this case "user error", but the problem is, it's not that
hard to be missing Vulkan drivers for one architecture, while debugging this
took way too long. It'd be nice to at least have some way of printing a
message.
The basic problem is that when Vulkan is present we retrieve the PCI IDs from
it, but when it's absent we set them to zero. As a result we end up creating
two different sets of registry entries, but only the 64-bit one gets populated
via initialize_display_settings(). EnumDisplayDevices() tries to access it and
finds the GPU entries empty.
This does lead me to ask: can we avoid querying GPUs in each process? Can we
just let explorer.exe manage them and get our information from there?
CC'ing Jacek and Zhiyi as both having worked closely with this code.
--
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.