Search Criteria
Package Details: picoscope7 7.2.19.8969-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/picoscope7.git (read-only, click to copy) |
|---|---|
| Package Base: | picoscope7 |
| Description: | PicoScope 7 Test and Measurment Stable |
| Upstream URL: | https://www.picotech.com/downloads/linux |
| Licenses: | custom |
| Conflicts: | picoscope7beta |
| Provides: | picoscope7 |
| Submitter: | Schorsch |
| Maintainer: | Schorsch |
| Last Packager: | Schorsch |
| Votes: | 5 |
| Popularity: | 0.41 |
| First Submitted: | 2023-10-07 00:12 (UTC) |
| Last Updated: | 2026-04-24 02:01 (UTC) |
Dependencies (16)
- desktop-file-utils (desktop-file-utils-gitAUR)
- fuse2
- ps7_libpicocvAUR
- ps7_libpicoippAUR
- ttf-roboto (ttf-roboto-fontconfigAUR, ttf-roboto-variableAUR, ttf-google-fonts-typewolfAUR)
- which (which-gitAUR)
- ps7_libps2000AUR (optional) – Support for PicoScope 2000 series
- ps7_libps2000aAUR (optional) – Support for PicoScope 2000a series
- ps7_libps3000AUR (optional) – Support for PicoScope 3000 series
- ps7_libps3000aAUR (optional) – Support for PicoScope 3000a series
- ps7_libps4000AUR (optional) – Support for PicoScope 4000 series
- ps7_libps4000aAUR (optional) – Support for PicoScope 4000a series
- ps7_libps5000AUR (optional) – Support for PicoScope 5000 series
- ps7_libps5000aAUR (optional) – Support for PicoScope 5000a series
- ps7_libps6000AUR (optional) – Support for PicoScope 6000 series
- ps7_libps6000aAUR (optional) – Support for PicoScope 6000a series
Latest Comments
« First ‹ Previous 1 2 3 Next › Last »
OpusOne commented on 2025-04-18 12:27 (UTC)
Thanks for your updates. Unfortunately, in my case, the picoscope executable still exits early with a 126 error code.
Trying to debug this, the 'picoscope' executable actually links to /opt/picoscope/bin/picoscope, which is a bash script, which uses the notify-send tool and then runs the following command:
//opt/picoscope/lib/PicoScope.GTK $@ 2>&1 >/dev/null 2>&1 >/dev/null $@ 2>&1 >/dev/null 2>&1 >/dev/null
the redirections explain why I get no message at all when running it from the command line.
So, next I tried running /opt/picoscope/lib/PicoScope.GTK directly. But it can't be run: the permissions set for this file are:
-rw-r--r-- 1 root root
And error 126 from bash seems also to indicate a permission error, it just didn't click until I looked further as I didn't know that 'picoscope' was a bash script.
What's up with these permissions in /opt/picoscope/lib ?
Schorsch commented on 2025-04-17 21:34 (UTC)
Hey all, thanks for raising the issues. Picotech finally brought the stable in line with the Early Access, and I could remove the troublesome gtk-sharp dependency and apply the same library install fixes as on the Early Access. A quick test with my 3203D on Manjaro looks good. Let me know if anything is still broken.
nurber commented on 2025-04-17 12:05 (UTC) (edited on 2025-04-17 12:07 (UTC) by nurber)
same here, I see the below excerpt from generator error report...
<event time="17/04/25 07:52:28.093" category="ApplicationInfo" level="Info">Application 'PicoScope 7 T&M' (version 7.1.50.5594 X64) starting.</event> <event time="17/04/25 07:52:28.111" category="ID" level="Info">1B8DE91210AEB3DAA057C8B9F476AA89</event> <event time="17/04/25 07:52:28.112" category="Environment" level="Info">Failed to detect access rights</event> <event time="17/04/25 07:52:28.116" category="Environment" level="Info">OS Version - Linux Arch Linux</event> <event time="17/04/25 07:52:28.116" category="Environment" level="Info">.net Version - 9.0.4</event> <event time="17/04/25 07:52:28.117" category="ApplicationInfo" level="Info">Settings file version - 11.5.1</event> <event time="17/04/25 07:52:28.117" category="ApplicationInfo" level="Info">Preferences file version - 2.0.0</event> <event time="17/04/25 07:52:28.117" category="ApplicationInfo" level="Info">Probes file version - 1.0.0</event> <event time="17/04/25 07:52:28.117" category="ApplicationInfo" level="Info">Data file binary header version - 1</event> <event time="17/04/25 07:52:28.530" category="Environment" level="Info">Loaded libusb-1.0 ver. 1.0.28.11946</event> <event time="17/04/25 07:52:28.531" category="Environment" level="Info">USB Hotplug available</event> <event time="17/04/25 07:52:28.602" level="Info">Using default culture: English (United States).</event> <event time="17/04/25 07:52:28.934" category="Device" level="Info">Attempting to load psospa</event> <event time="17/04/25 07:52:28.935" level="Info">Checking driver 'psospa' exists in executable path '/opt/picoscope/lib/</event> <event time="17/04/25 07:52:28.936" level="Info">Driver not found 'psospa'</event> <event time="17/04/25 07:52:28.936" category="Device" level="Info">Finished loading psospa</event> <event time="17/04/25 07:52:28.936" level="Error">Driver for model PSOSPA not available, code DllNotFound</event> <event time="17/04/25 07:52:29.732" category="Exception" level="Error">Exception:System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.DllNotFoundException: Unable to load shared library 'picocv' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable: /opt/picoscope/lib/picocv.so: cannot open shared object file: No such file or directory /opt/picoscope/lib/libpicocv.so: cannot enable executable stack as shared object requires: Invalid argument /opt/picoscope/lib/picocv: cannot open shared object file: No such file or directory /opt/picoscope/lib/libpicocv: cannot open shared object file: No such file or directoryat Pico.Interop.OpenCV.Imports.InspectData(IntPtr dataPtr, Int32 length, Int32& width, Int32& height, Int32& channels) at Pico.Interop.OpenCV.PicoCV.PcvImage.InspectData(Byte[] data, Int32& width, Int32& heigth, Int32& channels) at PICM..(Byte[], Int32&, Int32&, Int32&) at Pico.Interop.Common.Drawing.PicoCVImageFactory.FromResourceId(String id) at Pico.Services.Themes.ThemedIcon1..ctor(String maskResourceId) at Pico.Services.Themes.UpDownIcon1..ctor(String maskResourceId) at PSV.ic..ctor(String a) at PSV.id.CreateThemedIcon(String a) at Pico.Services.Themes.ThemedIconProvider2.GetImage(String maskResourceId, ThemedIconState state, Nullable1 color) at PicoScope.GTK.Controls.Themed.PlusMinusImage.GetImage(String resourceId, ThemedIconState state) at PicoScope.GTK.Controls.Themed.ThemedImageBase.UpdateIcon() at PicoScope.GTK.Controls.Themed.ThemedImageBase.SetSizeRequest(Int32 width, Int32 height) at PicoScope.GTK.Controls.Themed.ThemedImageBase..ctor(Action1 callbackRegistrar, Action1 callbackRemover, String maskResourceId, Boolean isInverted, Int32 width, Int32 height)...OpusOne commented on 2025-04-17 11:38 (UTC)
Still no luck with 7.1.50. The app exits immediately, I get this message in the journal, with no further detail that I could find:
app-picotech\x2dpicoscope@aafdfd5be40244f6be93b93aa7b0902a.service: Main process exited, code=exited, status=126/n/a
patrigg commented on 2025-02-20 13:21 (UTC)
The crash now seems to occur because the picocv assembly is not found. This is the error I get:
vanbwodonk commented on 2025-02-06 00:02 (UTC)
Right now picoscope 7 crash even with
gtk-sharp-3 2.99.3-5masterX244 commented on 2025-01-26 10:06 (UTC)
A fix for that issue is inbound in the next update. It's already in the beta channel since a while
OpusOne commented on 2024-07-26 23:26 (UTC)
Ditto, same issue. Was going to post a comment about it, and saw there were already 8. :)
A3D commented on 2024-07-25 19:49 (UTC)
Hello,
I faced the exact same issue and I also was able to solve it by downgrading gtk-sharp to version 2.99.3-5.
Thanks rc0r for the hint :-)
rc0r commented on 2024-07-23 11:12 (UTC)
I tried picoscope7beta yesterday after all my other unsuccessful attempts. Unfortunately, it crashes with the same exception.
On my system
gtk-sharp-3is only used by Picoscope so it might be possible to explicitly specify the last known workinggtk-sharp-3version in the PKGBUILD file of Picoscope to work around the problem until it's fixed upstream. However, this might of course not be the right thing to do for other setups that have dependencies on an up-to-dategtk-sharp-3.« First ‹ Previous 1 2 3 Next › Last »