Package Details: picoscope7 7.2.19.8969-1

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)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3

Schorsch commented on 2024-07-23 10:34 (UTC)

Maybe you can try the picoscope7beta preview version to see if this got addressed already?

Schorsch commented on 2024-07-23 10:33 (UTC)

Thanks for the update, this would have been my first lead as well after comparing package versions between my system and yours, but I couldn't do any testing yet. I guess then it's only a matter of time until it breaks on my system too. I don't think there is much I can do about that on either the GTK-sharp or Picoscope side. I have to hope they figure it out. Maybe once it hits the official Ubuntu version.

rc0r commented on 2024-07-23 07:31 (UTC)

Downgrading gtk-sharp-3 from 3.22.2-1 to 2.99.3-5 fixes the issue for me:

sudo pacman -U /var/cache/pacman/pkg/gtk-sharp-3-2.99.3-5-x86_64.pkg.tar.zst

gtk-sharp-3-2.99.3-5 was the last version I had in my package cache. As I did not check any other package versions 2.99.3-5 might not be the last working version.

rc0r commented on 2024-07-23 06:31 (UTC)

Thanks for your efforts @Schorsch! I also installed picoscope on my home workstation after updating all Arch packages. Unfortunately, I'm seeing the same error. However on my office workstation Picoscope worked until yesterday before I upgraded. In 1 there is the pacman log of the updated packages. Please note, I had to downgrade linux and nvidia drivers due to an unrelated issue with multiple monitors. The downgrades should not be the cause of the Picoscope crash as I my home setup didn't require any downgrades and Picoscope was crashing still.

As suggested, I started Picoscope from the terminal mono /opt/picoscope/lib/PicoScope.GTK.exe 2>&1 > picoscope.log 2>&1 >> picoscope.log. The logs can be found in 2. These were captured after doing a clean reinstall of both picoscope (+deps) and the libs required to operate the scope I'm using.

Let me know if there's anything else I could try.

Schorsch commented on 2024-07-22 16:50 (UTC)

@rc0r Hi, sorry for the trouble, but unfortunately I cannot reproduce the issue on my end. I started my old Manjaro VM that I used to build this package. The old version of Picoscope I had installed still ran fine, so I updated to the latest Picoscope, no change. After also installing 900something system updates and a few reboots, still no problem (though I had to manually update libps3000a as well for my scope, no crashes though, the scope just wasn't being detected until I updated the device library). Finally I completely removed all Picoscope related packages and remaining config files and did a clean reinstall. All still working fine.

Maybe you can share some more details about your system, try launching Picoscope from a terminal to see if you get any more helpful output or try a clean reinstall of Picoscope?

rc0r commented on 2024-07-22 09:09 (UTC)

After a recent system upgrade picoscope7 crashes with the following on startup:

Exception:GLib.MissingIntPtrCtorException: Unable to construct instance of type PSV.zo from native object handle. Instance of managed subclass may have been prematurely disposed.
  at GLib.ObjectManager.CreateObject (System.IntPtr raw) [0x00064] in <dd0cdd755d2541d5880043addb57cbac>:0 
  at GLib.Object.GetObject (System.IntPtr o, System.Boolean owned_ref) [0x000b0] in <dd0cdd755d2541d5880043addb57cbac>:0 
  at GLib.Value.op_Explicit (GLib.Value val) [0x00007] in <dd0cdd755d2541d5880043addb57cbac>:0 
  at GLib.Value.get_Val () [0x0033e] in <dd0cdd755d2541d5880043addb57cbac>:0 
  at GLib.SignalClosure.MarshalCallback (System.IntPtr raw_closure, System.IntPtr return_val, System.UInt32 n_param_vals, System.IntPtr param_values, System.IntPtr invocation_hint, System.IntPtr marshal_data) [0x00048] in <dd0cdd755d2541d5880043addb57cbac>:0

Any clues?

« First ‹ Previous 1 2 3