https://bugs.winehq.org/show_bug.cgi?id=9221
--- Comment #45 from madbad82(a)gmail.com ---
Created attachment 57214
--> https://bugs.winehq.org/attachment.cgi?id=57214
console log with +dinput (and the experimental logitec driver)
--
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=39988
Bug ID: 39988
Summary: winepath -w wrong output with path longer 260
Product: Wine
Version: 1.9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: s3141p(a)gmail.com
Distribution: ---
When the input $pathname is longer than 260 characters wine -w $pathname
1. truncates the converted output path at 260 characters
2. appends some garbage characters to it
3. reports no error and exits with status 0
I think fixing #3 as a minimum is important; at least exit 1, possibly print an
error message.
Fixing #2? Why is it printing garbage characters? Buffer overrun?
And please consider changing #1 by extending support to paths > 260 characters.
After all, if I convert the same path by hand and feed it to a Windows
application it has no problems dealing with it. So the 260-character limit of
winepath -w seems rather artificial to me.
I create long linux paths with
mkdir -p /tmp/aaa/bbb/ccc/ddd/eee/
touch /tmp/aaa/bbb/ccc/ddd/eee/$(dd if=/dev/zero count=1 bs=260 | tr '\000' a)
# which creates /tmp/aaa/bbb/ccc/ddd/eee/aaaaaaaa...
Thanks.
--
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=36199
Bug ID: 36199
Summary: valgrind shows several warnings under
crypt32/tests/chain.c
Product: Wine
Version: 1.7.17
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Created attachment 48320
--> https://bugs.winehq.org/attachment.cgi?id=48320
valgrind log
A few in glibc:
==17802== Thread 2:
==17802== Invalid read of size 1
==17802== at 0x40187FA: strcmp (strcmp.S:34)
==17802== by 0x4008925: _dl_map_object (dl-load.c:2113)
==17802== by 0x4013383: dl_open_worker (dl-open.c:224)
==17802== by 0x400F1F5: _dl_catch_error (dl-error.c:187)
==17802== by 0x4012D93: _dl_open (dl-open.c:650)
==17802== by 0x435093A: do_dlopen (dl-libc.c:87)
==17802== by 0x400F1F5: _dl_catch_error (dl-error.c:187)
==17802== by 0x4350A2A: dlerror_run (dl-libc.c:46)
==17802== by 0x4350AB0: __libc_dlopen_mode (dl-libc.c:163)
==17802== by 0x4221819: pthread_cancel_init (unwind-forcedunwind.c:52)
==17802== by 0x42219FB: _Unwind_ForcedUnwind (unwind-forcedunwind.c:129)
==17802== by 0x421F732: __pthread_unwind (unwind.c:129)
==17802== by 0x421A080: pthread_exit (pthreadP.h:280)
==17802== by 0x7BC8E1A9: terminate_thread (thread.c:349)
==17802== by 0x7BC87009: ??? (signal_i386.c:2571)
==17802== by 0x6A5F357: ???
==17802== by 0x4218F92: start_thread (pthread_create.c:309)
==17802== by 0x431D7ED: clone (clone.S:129)
==17802== Address 0x693d913 is on thread 1's stack
==17802==
==17802== Invalid read of size 4
==17802== at 0x4352239: _Unwind_IteratePhdrCallback
(unwind-dw2-fde-glibc.c:112)
==17802== by 0x43503E2: dl_iterate_phdr (dl-iteratephdr.c:76)
==17802== by 0x4352AF9: _Unwind_Find_FDE (unwind-dw2-fde-glibc.c:267)
==17802== by 0x6B9E336: ??? (in
/usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/32/libgcc_s.so.1)
==17802== by 0x6B9EB21: ??? (in
/usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/32/libgcc_s.so.1)
==17802== by 0x6B9F10F: _Unwind_ForcedUnwind (in
/usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/32/libgcc_s.so.1)
==17802== by 0x42219F1: _Unwind_ForcedUnwind (unwind-forcedunwind.c:137)
==17802== by 0x421F732: __pthread_unwind (unwind.c:129)
==17802== by 0x421A080: pthread_exit (pthreadP.h:280)
==17802== by 0x7BC8E1A9: terminate_thread (thread.c:349)
==17802== by 0x7BC87009: ??? (signal_i386.c:2571)
==17802== by 0x6A5F357: ???
==17802== by 0x4218F92: start_thread (pthread_create.c:309)
==17802== by 0x431D7ED: clone (clone.S:129)
==17802== Address 0x693c034 is on thread 1's stack
==17802==
==17802== Thread 1 crypt32_test.exe.so:
==17802== Jump to the invalid address stated on the next line
==17802== at 0x693E820: ??? (in /lib32/libresolv-2.19.so)
==17802== by 0x425F4E8: __run_exit_handlers (exit.c:82)
==17802== by 0x425F54C: exit (exit.c:104)
==17802== by 0x7BC68772: NtTerminateProcess (process.c:63)
==17802== by 0x7BC5941B: RtlExitUserProcess (loader.c:2538)
==17802== by 0x7B868D09: ??? (process.c:2668)
==17802== Address 0x693e820 is on thread 1's stack
==17802==
and several possible leaks:
==17802== 20 bytes in 1 blocks are possibly lost in loss record 50 of 427
==17802== at 0x7BC4C6B7: notify_alloc (heap.c:255)
==17802== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716)
==17802== by 0x514398B: CryptMemAlloc (main.c:124)
==17802== by 0x511E0A9: CertAddStoreToCollection (collectionstore.c:519)
==17802== by 0x5164B4B: CRYPT_SysOpenStoreW (store.c:592)
==17802== by 0x5165ADF: CertOpenStore (store.c:907)
==17802== by 0x51136FD: CRYPT_CreateChainEngine (chain.c:130)
==17802== by 0x511394F: get_chain_engine (chain.c:175)
==17802== by 0x511ADC0: CertGetCertificateChain (chain.c:2894)
==17802== by 0x4E618AA: testVerifyCertChainPolicy (chain.c:4790)
==17802== by 0x4E61C4C: func_chain (chain.c:4844)
==17802== by 0x4EB7F67: run_test (test.h:584)
==17802== by 0x4EB8356: main (test.h:654)
==17802==
==17802== 60 bytes in 3 blocks are possibly lost in loss record 197 of 427
==17802== at 0x7BC4C6B7: notify_alloc (heap.c:255)
==17802== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716)
==17802== by 0x514398B: CryptMemAlloc (main.c:124)
==17802== by 0x5157661: ContextPropertyList_SetProperty (proplist.c:132)
==17802== by 0x515788F: ContextPropertyList_Copy (proplist.c:215)
==17802== by 0x511E9AF: Context_CopyProperties (context.c:130)
==17802== by 0x510AB6C: Cert_clone (cert.c:139)
==17802== by 0x5163664: MemStore_addContext (store.c:151)
==17802== by 0x5163A35: MemStore_addCert (store.c:243)
==17802== by 0x510B119: add_cert_to_store (cert.c:263)
==17802== by 0x510B27F: CertAddCertificateContextToStore (cert.c:287)
==17802== by 0x510A852: CertAddEncodedCertificateToStore (cert.c:65)
==17802== by 0x515E94A: add_ms_root_certs (rootstore.c:732)
==17802== by 0x515EB12: create_root_store (rootstore.c:808)
==17802== by 0x515EC6C: CRYPT_RootOpenStore (rootstore.c:829)
==17802== by 0x516435C: CRYPT_SysRegOpenStoreW (store.c:435)
==17802== by 0x5165ADF: CertOpenStore (store.c:907)
==17802== by 0x5164BAF: CRYPT_SysOpenStoreW (store.c:604)
==17802== by 0x5165ADF: CertOpenStore (store.c:907)
==17802== by 0x51136FD: CRYPT_CreateChainEngine (chain.c:130)
==17802==
==17802== 96 bytes in 1 blocks are possibly lost in loss record 294 of 427
==17802== at 0x7BC4C6B7: notify_alloc (heap.c:255)
==17802== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716)
==17802== by 0x61ACD34: heap_alloc_zero (internet.h:121)
==17802== by 0x61ADCA1: create_netconn (netconnection.c:369)
==17802== by 0x619CFF2: open_http_connection (http.c:4826)
==17802== by 0x619D68C: HTTP_HttpSendRequestW (http.c:4972)
==17802== by 0x619EE2C: HttpSendRequestExW (http.c:5511)
==17802== by 0x61643F8: HTTP_RetrieveEncodedObjectW (cryptnet_main.c:933)
==17802== by 0x6165930: CryptRetrieveObjectByUrlW (cryptnet_main.c:1479)
==17802== by 0x5118CA0: CRYPT_FindIssuer (chain.c:2039)
==17802== by 0x51193A2: CRYPT_GetIssuer (chain.c:2168)
==17802== by 0x511952F: CRYPT_BuildSimpleChain (chain.c:2200)
==17802== by 0x511976F: CRYPT_GetSimpleChainForCert (chain.c:2247)
==17802== by 0x5119885: CRYPT_BuildCandidateChainFromCert (chain.c:2277)
==17802== by 0x511AE8B: CertGetCertificateChain (chain.c:2914)
==17802== by 0x4E5F02E: testGetCertChain (chain.c:3996)
==17802== by 0x4E61C51: func_chain (chain.c:4845)
==17802== by 0x4EB7F67: run_test (test.h:584)
==17802== by 0x4EB8356: main (test.h:654)
==17802==
etc. (full log attached)
--
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=4825
David Gerard <dgerard(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dgerard(a)gmail.com
--- Comment #30 from David Gerard <dgerard(a)gmail.com> ---
Still valid Wine 2.1.0 (from Ubuntu 16.04 x86-64 PPA).
Native comctl32.dll from winetricks doesn't seem to bring up radio channels or
option to add them.
(Note that radio channels do play if you open them by their URL directly.)
--
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=9221
--- Comment #44 from Bruno Jesus <00cpxxx(a)gmail.com> ---
(In reply to madbad82 from comment #43)
> Created attachment 57205 [details]
> backtrace
>
> Backtrace of "wine control" with the experimental KLGDFF Logitec driver
There are some well-known crashes in joy.cpl but since my controllers don't
support the other effects I can't reproduce myself so it is good that you can
test this. If you are able to compile Wine I can attach some patches.
Anyway, please attach a +dinput patch when playing with all effects
sequentially.
--
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=9221
--- Comment #43 from madbad82(a)gmail.com ---
Created attachment 57205
--> https://bugs.winehq.org/attachment.cgi?id=57205
backtrace
Backtrace of "wine control" with the experimental KLGDFF Logitec driver
--
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=9221
--- Comment #42 from madbad82(a)gmail.com ---
Created attachment 57204
--> https://bugs.winehq.org/attachment.cgi?id=57204
console log
Console log from "wine control" with the experimental KLGDFF Logitec driver
--
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=9221
madbad82(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |madbad82(a)gmail.com
--- Comment #41 from madbad82(a)gmail.com ---
Hi guys.
Just to let you know that there is an experimental driver (KLGDFF) for Logitec
wheels in the work with support for other effects other than the "Constant
force" one.
I've got this experimental driver from here:
http://steamcommunity.com/groups/linuxff/discussions/0/405692224235574471/
The driver seems to work with some native game like Euro Truck Simulator 2
(still buggy but work).
If I launch "wine control" I see those effects reported as available:
1 Constant force
2 Square
3 Sine
4 Triangle
5 SawtoothUp
6 SawtoothDown
7 Spring
8 Damper
9 Inertia
10 Friction
Playing the effects works for the effects from 1 to 6 (with some errors, see
console-log.txt) but I get a crash if I try the effects from 7 to 10 (see
wine-backtrace.txt).
I'm not sure if the bug is caused by wine or if it is due to the "experimental"
state of the driver.
I would really like to play properly rFactor2 via wine.
Any help is appreciated, even an "is not our bug" so I can report the problem
to the driver developer!
Thanks in advance.
--
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=35490
Bug ID: 35490
Summary: After SimCity 2013 updates:
d3d_shader:shader_sm4_read_src_param Unhandled swizzle
type 0.
Product: Wine
Version: 1.7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: eric.ladner(a)gmail.com
Classification: Unclassified
Created attachment 47376
--> http://bugs.winehq.org/attachment.cgi?id=47376
basic output on the command line
It used to run ok (although both Origin and SimCity were a nightmare to
install).
After a recent update, though when starting SimCity it never shows the splash
screen and spews this until you kill the process:
fixme:d3d_shader:shader_sm4_read_src_param Unhandled swizzle type 0.
I let it run for about 10 seconds and it spit out 11 million errors (log
attached).
If you want a more detailed log, let me know what options you'd like.
--
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=41637
Bug ID: 41637
Summary: Altium Designer 16: Wineserver stuck / not responding
since 1.9.2*
Product: Wine
Version: 1.9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: afb(a)mailbox.org
Distribution: ---
Altium Designer 16 stopped working since Wine 1.9.2* / Arch Linux 64.
After updating from Wine 1.9.19 to 1.9.22, neither Altium 16.1.12 in present
prefixes, nor Altium installer in new prefixes starts anymore. Instead,
/usr/bin/wineserver gets stuck at full cpu load and does not react to
wineserver -k or SIGTERM.
What was also done:
- purge and reinstall of Wine and all dependencies
- switch of Wine-staging 1.9.21
- log in as different (new) user
- downgrading to Wine 1.9.20
- setup of a chroot environment on a second hdd with nothing more than Xorg,
drivers and Wine / dependencies
... without improvement of the situation
Link to the recent Altium installer:
https://s3.amazonaws.com/altium-release-manager/Altium_Designer_16/AltiumDe…
In general, Wine seems to work, which was tested with Notepad++ from:
https://notepad-plus-plus.org/download/v7.1.html
--
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.