Package Details: picoscope7 7.1.50_1r5594-2

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: 2
Popularity: 0.58
First Submitted: 2023-10-07 00:12 (UTC)
Last Updated: 2025-04-17 20:37 (UTC)

Dependencies (16)

Required by (0)

Sources (1)

Latest Comments

1 2 3 Next › Last »

OpusOne commented on 2025-04-18 14:16 (UTC)

When does the 'postinst' script get called?

Schorsch commented on 2025-04-18 14:12 (UTC)

@OpusOne Sorry, not sure what to tell you. I just did a clean Arch install, installed Picoscope7 with Pamac/pamac-aur and it just worked... Maybe just try to manually chmod +x /opt/picoscope/lib/PicoScope.GTK ?

OpusOne commented on 2025-04-18 13:42 (UTC)

No error that I noticed. I am on Arch directly. I don't think that makes a difference, but I use aurutils to install/update AUR packages.

I'm looking at the /opt/picoscope/scripts/picoscope7_postinst script to try and figure out this permission issue.

Schorsch commented on 2025-04-18 12:40 (UTC)

@OpusOne Not sure what's with the permissions, I don't explicitly touch them. The postinst script from the deb package should take care of setting PicoScope.GTK as executable on line 29. For me the installed binary correctly ends up as

-rwxr-xr-x 1 root root 179203399 Apr 18 14:31 /opt/picoscope/lib/PicoScope.GTK

and I can run it directly like this. Not sure why you don't get x permissions. What OS are you running, so I can try to reproduce the issue? Did you get any error during installation regarding the postinst step?

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 directory

at 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:

(PicoScope.GTK:41836): Gtk-CRITICAL **: 14:15:55.251: gtk_main_quit: assertion 'main_loops != NULL' failed
[ERROR] FATAL UNHANDLED 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: picocv assembly:<unknown assembly> type:<unknown type> member:(null)
  at (wrapper managed-to-native) Pico.Interop.OpenCV.Imports.InspectData(intptr,int,int&,int&,int&)
  at Pico.Interop.OpenCV.PicoCV.PcvImage.InspectData (System.Byte[] data, System.Int32& width, System.Int32& heigth, System.Int32& channels) [0x00014] in <ef5590eb7b8fc57912aa45e68dc07163>:0
  at Pico.Interop.Common.Drawing.PicoCVImageFactory.FromResourceId (System.String id) [0x0003d] in <1e742560f91a5a6ac7dd462358ae3f6c>:0
  at Pico.Services.Themes.ThemedIcon`1[TImage]..ctor (System.String maskResourceId) [0x0004b] in <31116f9be9169880b5629966a99e4925>:0
  at Pico.Services.Themes.UpDownIcon`1[TImage]..ctor (System.String maskResourceId) [0x00000] in <31116f9be9169880b5629966a99e4925>:0
  at PSV.hx..ctor (System.String a) [0x00000] in <9f7e35a9e29a33ee18c58ffc9bfba9ae>:0
...

vanbwodonk commented on 2025-02-06 00:02 (UTC)

Right now picoscope 7 crash even with gtk-sharp-3 2.99.3-5