deepspace@Hal9000:~$ sudo apt-get install picoscope[sudo] password for deepspace: Reading package lists... DoneBuilding dependency tree Reading state information... DoneSome packages could not be installed. This may mean that you haverequested an impossible situation or if you are using the unstabledistribution that some required packages have not yet been createdor been moved out of Incoming.The following information may help to resolve the situation:

The following packages have unmet dependencies: picoscope : Depends: picomono but it is not going to be installedE: Unable to correct problems, you have held broken packages.deepspace@Hal9000:~$ sudo apt-get install picomonoReading package lists... DoneBuilding dependency tree Reading state information... DoneSome packages could not be installed. This may mean that you haverequested an impossible situation or if you are using the unstabledistribution that some required packages have not yet been createdor been moved out of Incoming.The following information may help to resolve the situation:

The following packages have unmet dependencies: picomono : Depends: libcairo2 (>= 1.12.0) but 1.10.2-6.1ubuntu3 is to be installedE: Unable to correct problems, you have held broken packages.

as far as I understand the problem is related to libcairo2 that on ubuntu 12.04 is 1.10.2-6 instead of >=1.12.0 as required.Some suggestions?thanks a lotgianni.

Looks like permission issue? Things to check:* Is you user member of group pico ? Run `groups` command to verify this.* Is device having correct permissions set up? Run /opt/picoscope/share/doc/libps2000a/usbtest script to verify* Is udev config present and active? Check for /etc/udev/rules.d/95-pico.rules file

Maybe reboot is all you need. You can also try to reapply the permissions

This script looks for Pico USB devices connected to your computerand checks whether you are able to access them. If your user accountdoes not have permission to access the devices, the script will tryto suggest how to correct this for your particular Linux installation.

Press enter to continue...

Getting user and group information... - You are running this script as deepspace. - You are in the following groups: deepspace adm dialout cdrom sudo audio dip plugdev lpadmin sambashare pico

Please connect your Pico USB device and press enter to continue...

Pico USB device found: /dev/bus/usb/003/002

- It belongs to root (which is not you) who has permissions rw- - The members of group pico (which you are in) have permissions rw- - Everyone else has permissions r-- - You can write to this device and so will be able to use it.

I've done a reboot too but when I start picoscope (after the editing you suggested in the /opt/picoscope/bin/picoscope script ) I ear the relay clicking on the picoscope hardware but it is still crashing (or some times hang with a blank picoscope window). The output of the script is the following: (sorry it is a bit long....)

=================================================================Got a SIGSEGV while executing native code. This usually indicatesa fatal error in the mono runtime or one of the native libraries used by your application.=================================================================

Looking at the stack, it seems that you have some sort of unsupported settings in the signal generator.Does picoscope work ok, when using only demo device? You can then reset default startup settings.Alternatively you could look into your home folder for .local/share and rename or move Pico Technology folder to see if it helps.

If demo mode works, the the software side is more likely to be OK. I run several tests with your scope model and didn't run into any problems. How about going into demo, waiting for it to start, the plugin the device and try open it via File -> Connect device?Did you try the scope on different system, preferably running Windows with PicoScope 6 on it? It is also possible that your USB port / hub /cable are damaged, as after clicking the relays device starts to draw more current, which may cease the communication.

Mariofirst of all thank you for all your suggestions.following are my answers:I started in demo mode and then connected device.... result: crashI suspect that the key is in the last line of the syslog attached "mono did not claim interface 0 before use"

in fact, starting from last software release of picoscope 6, I have the message: "Not all updates can be installed"from update manager of the laptop (I assume it is the picomono/libcairo2 dependencies you already solved) but I prefer not doing any update

also when I bought picoscope (January 2014) I installed the software on the desktop and it was running: it is connected to a USB hub with external power supply (2.5Amps)

definitely I think I should upgrade my system to ubuntu 14.04 or 16.04 but I'm now in the middle of an important project and I prefer remain in 12.04.

For the moment I use the scope on the desktop through the laptop via network and it works fine, only a little slow....