@Schorsch: I think they fixed a few things in their packaging pipeline which made the postinst stuff obsolete.

I updated the PKGBUILD so it should build again. Not sure if there might be any functionality missing that was previously in the postinst script, but they seemed to either have removed or moved it somewhere I can't find it :)

@masterX244, Yea I noticed that too and I've started to troubleshoot it, however they either changed more things or something is simply wrong with the Picotech packages. I'll have to do some testing to see if everything still works if I just ignore all that stuff...

there are some breaking changes inside the package, the .deb changed a few things around. Build fails. (the stuff from line 38 to 45 of the pkgbuild is not working anymore)

@Schorsch I'm not on a fresh picoscope install so maybe that is the issue? I've installed it about 5 or 6 months ago.

@SadiQ Maybe I missed something, but this should already be done by the install script on the library package. I may have to double check...

Ok. Based on the picoscope7 thread it seems that someone smarter used the following which works for me:

cd /opt/picoscope/lib
for f in *.so*; do sudo patchelf --clear-execstack "$f" ; done

Now picoscope starts for me.

It seems that after some updates picoscope won't start for me: [sadiq@arch ~]$ /opt/picoscope/lib/PicoScope.GTK

(PicoScope:2985): Gtk-CRITICAL **: 07:39:20.072: gtk_main_quit: assertion 'main_loops != NULL' failed
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: 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

I do see those links in the lib directory:

[sadiq@arch lib]$ ls *.so
.rw-r--r-- root root 1.8 MB Sun Jun 15 18:14:31 2025  libiomp5.so
lrwxrwxrwx root root  18 B  Sun Jun 15 18:14:34 2025  libpicocv.so ⇒ libpicocv.so.1.0.0
lrwxrwxrwx root root  19 B  Sun Jun 15 18:14:31 2025  libpicoipp.so ⇒ libpicoipp.so.1.0.1
lrwxrwxrwx root root  18 B  Sun Jun 15 18:15:09 2025  libps2000.so ⇒ libps2000.so.2.0.0
lrwxrwxrwx root root  19 B  Sun Jun 15 18:15:05 2025  libps2000a.so ⇒ libps2000a.so.2.0.0

And some more links:

[sadiq@arch lib]$ ls *.so.*
lrwxrwxrwx root root  18 B  Sun Jun 15 18:14:34 2025  libpicocv.so.1 ⇒ libpicocv.so.1.0.0
.rw-r--r-- root root  46 MB Sun Jun 15 18:14:34 2025  libpicocv.so.1.0.0
lrwxrwxrwx root root  19 B  Sun Jun 15 18:14:31 2025  libpicoipp.so.1 ⇒ libpicoipp.so.1.0.1
.rw-r--r-- root root  24 MB Sun Jun 15 18:14:31 2025  libpicoipp.so.1.0.1
lrwxrwxrwx root root  18 B  Sun Jun 15 18:15:09 2025  libps2000.so.2 ⇒ libps2000.so.2.0.0
.rw-r--r-- root root 987 KB Sun Jun 15 18:15:09 2025  libps2000.so.2.0.0
lrwxrwxrwx root root  19 B  Sun Jun 15 18:15:05 2025  libps2000a.so.2 ⇒ libps2000a.so.2.0.0
.rw-r--r-- root root 7.6 MB Sun Jun 15 18:15:05 2025  libps2000a.so.2.0.0

I saw an error when running a script:

[sadiq@arch scripts]$ ./picoscope7beta_postinst
[sudo] password for sadiq:
ldconfig: Can't create temporary cache file /etc/ld.so.cache~: Permission denied

I did run all the scripts in /opt/picoscope/scripts/ with sudo and I didn't see any error from them after that. I also added +x on the .so.1.0.* files and that still didn't work. Any tips on what I missed?

Regarding the "File was saved on a PS3406B device" error and Send Report dialog on close, this can be fixed simply by saving a new "User Default PS Settings" file (Save button on the toolbar). I also had that damn bug for a long time, trying to find WHERE that file-saved-on-a-PS3406B-device could be... seems like it refers to the default config.

I don't get an entry for a Pico Bootloader...

When I first connect the scope I get

Mai 11 11:02:40 -- kernel: usb 1-2.4: new high-speed USB device number 9 using xhci_hcd
Mai 11 11:02:40 -- kernel: usb 1-2.4: New USB device found, idVendor=0ce9, idProduct=1213, bcdDevice= 1.00
Mai 11 11:02:40 -- kernel: usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mai 11 11:02:40 -- kernel: usb 1-2.4: Product: WestBridge 
Mai 11 11:02:40 -- kernel: usb 1-2.4: Manufacturer: Cypress
Mai 11 11:02:40 -- kernel: usb 1-2.4: SerialNumber: 0000000004BE

And then when starting the application:

Mai 11 11:03:10 -- systemd[918]: Started PicoScope 7 - PicoScope 7.
Mai 11 11:03:15 -- kernel: usb 1-2.4: USB disconnect, device number 9
Mai 11 11:03:15 -- kernel: usb 2-2.4: new SuperSpeed USB device number 4 using xhci_hcd
Mai 11 11:03:15 -- kernel: usb 2-2.4: LPM exit latency is zeroed, disabling LPM.
Mai 11 11:03:15 -- kernel: usb 2-2.4: New USB device found, idVendor=0ce9, idProduct=1213, bcdDevice= 0.32
Mai 11 11:03:15 -- kernel: usb 2-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mai 11 11:03:15 -- kernel: usb 2-2.4: Product: PicoScope 4000 Series PC Oscilloscope
Mai 11 11:03:15 -- kernel: usb 2-2.4: Manufacturer: Pico Technology Ltd
Mai 11 11:03:16 -- kernel: usb 2-2.4: reset SuperSpeed USB device number 4 using xhci_hcd
Mai 11 11:03:16 -- kernel: usb 2-2.4: LPM exit latency is zeroed, disabling LPM.
Mai 11 11:03:19 -- kernel: usb 2-2.4: reset SuperSpeed USB device number 4 using xhci_hcd
Mai 11 11:03:19 -- kernel: usb 2-2.4: LPM exit latency is zeroed, disabling LPM.

No idea why it says "PicoScope 4000". I have a 3203D and only have the 3000a driver installed.