Package Details: ltspice 17.20210604.1-1

Git Clone URL: (read-only, click to copy)
Package Base: ltspice
Description: SPICE simulator, schematic capture and waveform viewer. Installation based on Field Update Utility.
Upstream URL:
Licenses: custom
Submitter: M4a1x
Maintainer: jhbruhn
Last Packager: jhbruhn
Votes: 26
Popularity: 0.72
First Submitted: 2015-07-08 21:35
Last Updated: 2021-06-05 08:46

Latest Comments

1 2 3 4 Next › Last »

jhbruhn commented on 2021-06-05 08:42

Good catch, I updated the launcher to use the file in /usr/lib/wine/x86_64-windows/start.exe. After that, I had to delete my users Wine prefix (~/.ltspice/env) for the application to start successfully.

barabas commented on 2021-06-05 08:09

Replacing /usr/lib/wine/start.exe with just wine.exe seems to fix the script. Looks like the file was moved to /usr/lib/wine/x86_64-windows/start.exe.

I'm not familiar with wine, but there are other start.exe files in the prefix folder. Isn't this the one we want to run here?

Auracle commented on 2021-05-27 07:18

Hi. I am facing the following problem. The installation is successful without any hiccups. Note that I am running this with wine version wine-6.9 and after complete upgrade of the system. When I try to execute LTSpice using the .desktop file nothing happens. Then I try running it by executing ltspice I get the following error.

wine: failed to open "/usr/lib/wine/start.exe": c0000135

The trying

wine /usr/lib/wine/start.exe /unix /opt/ltspice/XVIIx64.exe
export WINEPREFIX=$HOME/.ltspice/env WINEARCH=win64 && wine /opt/ltspice/XVIIx64

gives the same error.

Finally, running

wine /opt/ltspice/XVIIx64.exe

starts the application as intended. However, I see the following error 0104:err:module:open_builtin_so_file failed to load .so lib "/usr/lib/wine/x86_64-unix/" along with some extra information (not sure if it is relevant warnings or just logs. I am posting it for your info.)

0104:err:module:open_builtin_so_file failed to load .so lib "/usr/lib/wine/x86_64-unix/"
0104:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0104:fixme:ver:GetCurrentPackageId (00000000009A0590 0000000000000000): stub
0104:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub
0104:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub
0104:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub
0104:fixme:shell:InitNetworkAddressControl stub

I hope any readers of this post can suggest me on how to go about solving this problem. Thank you for creating and maintaining the package.

jhbruhn commented on 2021-04-14 16:29

Thanks for the hint dreieck, I moved the download of files into the prepare section as they change unpredictably depending on the file listing from the LTSpice website.

dreieck commented on 2021-04-14 13:54

In your PKGBUILD, you explicitly download stuff in build().

However, it is not recommended if stuff can already be downloaded via source-array or in prepare(), so that once makepkg -o is done no internet connection is needed to build the software.

Ideally, you could transfer all needed downloads to the source-array (the array beeing built "on the fly" by parsing "${_update_url}/release.log.gz"), or if that does not really work move the relevant parts now in build() into prepare().

Thanks for maintaining!

==> Starting build()...
Checking cache and downloading using 16 threads.
Download Progress: 5957/9785 (lib/sym/Comparators/LTC6754.asy)

jhbruhn commented on 2021-04-07 18:07

Thanks a lot lightspot21!

I have found that running wine /usr/lib/wine/start.exe /unix /opt/ltspice/XVIIx64.exe works as well and without the need to modify the prefix, so I will include that in the launcher script until the new wine version with the bugfix is released. Thanks again!

lightspot21 commented on 2021-04-07 17:47

Reposting due to accidental deletion.

So I went to hunt the issue behind the breakage:

I tried to run the 64-bit executable directly, just like the shell script. No WINEPREFIX set yet. wine /opt/ltspice/XVIIx64

and I get back the error: wine: failed to open L"/opt/ltspice/XVIIx64": c0000135

Attempting to "fake" the first run, I deleted the prefix and started anew: export WINEPREFIX=$HOME/.ltspice/env WINEARCH=win64 && wine /opt/ltspice/XVIIx64 but the error persisted.

With the same prefix, but calling wine /opt/ltspice/XVIIx64.exe the error changes to: wine: failed to load start.exe: 40000003

Googling it took me to this issue: , where the workaround was to copy start.exe from the command dir of the prefix to the system32 dir, then use wine start /unix /opt/ltspice/XVIIx64.exe with the correct prefix set to run the 64 bit version. This is because:

What has changed is that Wine is more strict about requiring the 
file to execute to actually be found on disk. By default, start.exe
is installed into c:\windows\command, which is not in the standard path, 
so it isn't found.

The bug is already fixed in the next version of Wine.

jhbruhn commented on 2021-04-02 13:08

I have tried multiple combinations of running the application but can't get it to work right now. I will sticky your workaround for now and if I find the time I'll figure out whether something is wrong with the launcher script.

Downgrading wine should also be a workaround but I haven't tried that.

Yazarai commented on 2021-03-28 16:19

@bigdino wine /opt/ltspice/XVIIx86.exe keeps doing it for me now that I tried it, even after a desktop session logout. Not sure whether this was your exact command but at least I guess I got myself a temporary workaround that hasn't failed yet.

bigdino commented on 2021-03-28 14:23

Same issue on my side as the previous comment.

I somehow managed to start LTSpice yesterday by calling /opt/ltspice/XVIIx86, but for some reason I can't start it anymore today.