Arch Linux User Repository

I should try that one of these days, I've usually just been testing on Manjaro, so maybe Arch is missing some dependencies out of the box that I take for granted... Thanks.

It's just plain vanilla arch, latest kernel, everything installed using the Installation Guide from the wiki (as I said..I can follow a tutorial and adapt some commands to give me less errors :) )

Yeah, I don't really know which driver goes for which scope, I have 3203D and I need the 3000a driver :) Glad you got it at least kinda running!

Also I meant to ask: What distro are you running on?

Fixed!!! Yes I did reinstall the package. I edited the file and I got a permission error:

[sadiq@arch ~]$ ls -ll /opt/picoscope/lib/PicoScope.GTK
.rw-r--r-- root root 170 MB Mon Feb 17 17:45:56 2025  /opt/picoscope/lib/PicoScope.GTK

It seems it belongs to root and it has no execute permissions.

I chmod +x that file and the app started, but it failed to detect my pico. I also needed to install some optional package. I have a pico 2205a so of course I installed the ps7b_libps2000a package but that didn't work as I obviously needed the ps7b_libps2000 package (or both) to get my scope working :)

All was great for about 5 minutes because the app crashed...but at least I could get it running :)

@Schorsch Thanks for your work and the help. Keep improving mate!

@SadiQ I assume you reinstalled the package after adding root to the suders file, so the postinst ran without error?

Try editing the picoscope binary (it's actually just a script that calls the main executable) with this command: sudo nano $(which picoscope)

Remove everything behind the $@ on the last line, save and then run picoscope from the terminal. This way you get its full output and maybe some more info about what's going wrong.

Alternatively just running /opt/picoscope/lib/PicoScope.GTK instead of picoscope should also work I guess.

@Schorsch I'm not new to linux, but I'm not a power user. I've been a noob linux user on and off for the last 20 years. I can follow tutorials and change a command here and there to show me less errors :) I actually think that this is my first ever comment on archlinux.

Now...back to the issue. I added root to /etc/sudoers for the simple fact that I saw it available in a /etc/sudoers.pacnew file on my system(I was probably supposed to do something with that file at some point...but I didn't get to it), and now picoscope got installed, but it doesn't run:

feb 20 19:10:23 arch systemd[1264]: Started PicoScope 7 - PicoScope 7.
feb 20 19:10:23 arch systemd[1264]: app-        picotech\x2dpicoscope@49ce632481734ed99189a6b8447d4f26.service: Main process exited,         code=exited, status=126/n/a
feb 20 19:10:23 arch systemd[1264]: app-       picotech\x2dpicoscope@49ce632481734ed99189a6b8447d4f26.service: Failed with result         'exit-code'.

Anything I can try?

@SadiQ New to this as in "new to Linux"? :)

All I can tell from your error is that apparently your install/distro seems to have issues if root runs a sudo command.

The postinst is a script in the package that runs after the install and sets up some device permissions. Apparently this contains a few commands with "sudo", which makes sense because root can set up permissions.

As you may know "sudo" is commonly used to run a single command as root even if you are not root. The sudoers file in /etc/sudoers controls who can do that and can even set some limits and options for it.

So obviously it's redundant to run a command with "sudo" if you're already root. Now usually I would expect that not to throw an error, because even though it's redundant, it can't really do more damage than you can already do if you're root.

So on one hand it makes no sense to have root in the sudoers file, but then again I can't think of a reason it would hurt.

All I can say is that if you're going to edit the sudoers file and you're new to all this, use the command visudo and don't directly open the file in a text editor, or you might learn what it means to lose all administrative access to your computer ;)

Hello. I just tried to install this and I get the following error :

::: Processing package changes...
(1/1) installing picoscope7beta                                                                           
[###############################################################] 100%
Running picoscope7beta deb postinst...
root is not in the sudoers file.
error: command failed to execute correctly
Optional dependencies for picoscope7beta
    //I removed some lines here
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Refreshing PackageKit...
(3/3) Updating the desktop file MIME type cache...

Any tips on what I can try? (I'm pretty new to this)

Thanks! It works great now.

Hey @vaar Thanks for commenting, I'm not using this package all that much these days but want to keep it up to date and functional.

gtk-sharp is no longer required for the beta version of Picoscope 7, and the "stable" version I currently consider broken until this requirement is removed there too upstream.

I don't think the error you're seeing has to do with gtk-sharp, but with the picocv and picoipp libraries themselves. I just updated those two packages to run execstack on the libraries during install to clear their executable stack flag. Not entirely sure if that is a good fix but it seems to do the trick for now. Let me know!