Re: Linux/Wine suddenly stopped working
I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- mholmes
Definitely not a Wine problem
This is definitely not caused by changes in Wine; the app was working fine, I did an update to WinSCP (with no change to Wine), and it stopped working. Other Wine apps continue to work. I presume an older version could be installed and would work, but given the current security climate I'm not comfortable installing older versions of Windows apps.
If WinSCP development has taken a turn that makes it incompatible with Wine, but there enough benefits that losing the Wine user base is worth it, then I'm fine with that; I'll just move to FileZilla and the command line. If, on the other hand, some random Delphi update has changed a background setting that has no bearing on the functionality of the app but happens to break Wine compatibility, I think there are probably lost of long-time users like me who would appreciate getting it back!
Cheers,
Martin
If WinSCP development has taken a turn that makes it incompatible with Wine, but there enough benefits that losing the Wine user base is worth it, then I'm fine with that; I'll just move to FileZilla and the command line. If, on the other hand, some random Delphi update has changed a background setting that has no bearing on the functionality of the app but happens to break Wine compatibility, I think there are probably lost of long-time users like me who would appreciate getting it back!
Cheers,
Martin
- Guest
Does an older WinSCP version still work? I don't see this directly specified. You only stated since the August update. Can't infer that means was tested.
The thing about Wine, and I say this although you used it 12 years with WinSCP, its a beast and newer software changes can find problems in Wine with either stubs not done or just stuff that doesn't yet exist in Wine. This is the downside to Wine, always has been, always will be for as long as Wine has to keep changing to newer Windows/software changes.
Wine also has another problem where the OS, driver, updates pulled etc can cause it to break. This is something many people don't get. The software to use with it can look broken but not be.
At the same time, I don't know if the log snippet you posted is a red herring or not. Wine errors can extremely be red herrings as logs are complicated and really require vast log and Wine debug knowledge.
Ideally, I would say that if an older WinSCP version works, use that. If its no longer working then you have a Wine running problem, not a WinSCP one.
The thing about Wine, and I say this although you used it 12 years with WinSCP, its a beast and newer software changes can find problems in Wine with either stubs not done or just stuff that doesn't yet exist in Wine. This is the downside to Wine, always has been, always will be for as long as Wine has to keep changing to newer Windows/software changes.
Wine also has another problem where the OS, driver, updates pulled etc can cause it to break. This is something many people don't get. The software to use with it can look broken but not be.
At the same time, I don't know if the log snippet you posted is a red herring or not. Wine errors can extremely be red herrings as logs are complicated and really require vast log and Wine debug knowledge.
Ideally, I would say that if an older WinSCP version works, use that. If its no longer working then you have a Wine running problem, not a WinSCP one.
- mholmes
Linux/Wine suddenly stopped working
I've been using WinSCP under Wine on Linux for maybe 12 years now -- I used it back when I used to be a Windows user and I've always liked it. But since the August update it's completely stopped working. I just installed the latest version, and when I start it, I get the errors below. Does anyone know what changed, and whether there might be a workaround for this?
All help appreciated,
Martin
Unhandled exception: 0x0eedfade in wow64 32-bit code (0x7b662597).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:006b GS:0063
EIP:7b662597 ESP:0191f354 EBP:0191f3a8 EFLAGS:00200246( - -- I Z- -P- )
EAX:0191f354 EBX:00000000 ECX:00000018 EDX:0191f3e0
ESI:011f862c EDI:0191f9ec
Stack dump:
0x0191f354: 0eedfade 00000001 00000000 7b662597
0x0191f364: 00000007 00000000 0399a120 00000000
0x0191f374: 00000000 00000000 00000000 00000000
0x0191f384: 009ea84c 038ee070 0191f3bc 0056f6f2
0x0191f394: 0191f3f8 0056f70d 0191f3bc 00000002
0x0191f3a4: 0191f9ec 0191f518 01063da2 0eedfade
Backtrace:
=>0 0x7b662597 RaiseException+0x42(code=<is not available>, flags=<is not available>, count=<is not available>, args=<is not available>) [/usr/src/wine-9.0~repack-4build3/dlls/kernelbase/debug.c:378] in kernelbase (0x0191f3a8)
1 0x01063da2 in winscp (+0xc63da2) (0x0191f518)
0x7b662597 RaiseException+0x42 [/usr/src/wine-9.0~repack-4build3/dlls/kernelbase/debug.c:378] in kernelbase: mov -0x04(%ebp), %ebx
Unable to access file '/usr/src/wine-9.0~repack-4build3/dlls/kernelbase/debug.c'
Modules:
Module Address Debug info Name (127 modules)
PE 400000- 1811000 Export winscp
ELF 5683e000-56843000 Deferred <wine-loader>
PE-Wine 76670000-7667f000 Deferred psapi
PE-Wine 76690000-766b8000 Deferred wtsapi32
PE-Wine 766d0000-767bc000 Deferred msctf
PE-Wine 767d0000-76850000 Deferred netapi32
PE-Wine 76860000-7689b000 Deferred msv1_0
PE-Wine 768b0000-768d9000 Deferred kerberos
PE-Wine 768f0000-7690e000 Deferred nsi
All help appreciated,
Martin