Test and Measurement Forum

Beta Release of PicoScope for Linux

Discussion forum for the new Picoscope Linux software

Re: Beta Release of PicoScope for Linux

Postby lohan » Tue Feb 10, 2015 8:04 am

I installed the new release PicoScope 6.10.1.36 under Opensuse 13.1 with mono 3.10.0, however I still get the same error and crash of PicoScope software. I tried to install the older version from August 2014, which didn't work either.
lohan
Active User
Active User
 
Posts: 7
Joined: Fri Oct 03, 2014 10:03 am

Re: Beta Release of PicoScope for Linux

Postby pipau » Fri Feb 13, 2015 7:52 am

picosope seems to works for now for me with OpenSuse 13.2 64bit (13.1 didn't work).
I had so install some mono-stuff via yast to prevent segfaults.
pipau
Newbie
 
Posts: 0
Joined: Tue Nov 25, 2014 7:00 pm

Re: Beta Release of PicoScope for Linux

Postby banneker2015 » Fri Feb 20, 2015 10:09 pm

Hi all,

New to Pico. Thought I would inform anyone that is considering the following Linux/Debian/Ubuntu(-ish) install for picoscope 2204A:

- Works fine (stable) so far under XFCE4 (32-bit) under Couton on a Chromebook (HP14). Just remember to use 'gksu picoscope' to start it up in the terminal. If you are familiar with Arduino IDE (sketches), it likes the same permissions, from my observation.

- Crashes under Mint 17.1 Cinnamon 64-bit after a few minutes. Well... it's on a 2006 iMac intel, but i'm thinking its the 64-bit OS part the software is having issues with... I'll get around to reinstalling a 32-bit version to see if that corrects the problem.

One question does come to mind: does this software prefers/uses java? On the Chromebook, I'm using Oracle. While on the Mint install, i'm using OpenJDKJava...
banneker2015
Newbie
 
Posts: 0
Joined: Fri Feb 20, 2015 9:43 pm

Re: Beta Release of PicoScope for Linux

Postby philton » Thu Mar 12, 2015 11:09 pm

I have downloaded the latest PicoScope 6 and installed it.
I still don't see anything under the tools menu other than Preferences.
Should the tools be there?
In particular I'm interested in decoding serial protocols. (One of the reasons I bought this scope)
Regards,
Paul Hilton
philton
Newbie
 
Posts: 0
Joined: Thu Mar 12, 2015 9:53 pm

Re: Beta Release of PicoScope for Linux

Postby Hitesh » Tue Mar 24, 2015 4:32 pm

Hi Paul,

The features available under the Tools menu in PicoScope 6 are only available in PicoScope 6 for for Windows at this moment in time.

The Serial Decoding feature has been undergoing some rework and should be available through the next PicoScope 6 for Windows Beta release. It should eventually make it into the Linux/Mac versions.

Regards,
Hitesh

Technical Specialist
Pico Technology
Hitesh
Site Admin
Site Admin
 
Posts: 2063
Joined: Tue May 31, 2011 3:43 pm
Location: St. Neots, Cambridgeshire

Re: Beta Release of PicoScope for Linux

Postby jcottier » Wed Mar 25, 2015 9:51 am

Hi, any time scales yet for when the full features will be available on trhe Linux version. Its been about a year now :(

Regards John.
jcottier
Active User
Active User
 
Posts: 8
Joined: Wed Mar 05, 2014 9:48 am

Re: Beta Release of PicoScope for Linux

Postby gde » Wed Jun 10, 2015 7:53 pm

hi,
i write this post because i have a problem with the new picoscope 2205 MSO. just open the picoscope application, the terminal shows the next lines and it crashs.

Code: Select all
gedoes@inspiron:~$ picoscope

(PicoScope.GTK:2674): GLib-CRITICAL **: Source ID 1 was not found when attempting to remove it

(PicoScope.GTK:2674): GLib-CRITICAL **: Source ID 2 was not found when attempting to remove it

(PicoScope.GTK:2674): Gtk-CRITICAL **: IA__gtk_widget_map: assertion 'gtk_widget_get_visible (widget)' failed

(PicoScope.GTK:2674): GLib-CRITICAL **: Source ID 490 was not found when attempting to remove it

(PicoScope.GTK:2674): GLib-CRITICAL **: Source ID 469 was not found when attempting to remove it

(PicoScope.GTK:2674): GLib-CRITICAL **: Source ID 492 was not found when attempting to remove it

(PicoScope.GTK:2674): GLib-CRITICAL **: Source ID 466 was not found when attempting to remove it

-----

(PicoScope.GTK:2674): GLib-CRITICAL **: Source ID 228402 was not found when attempting to remove it
Stacktrace:


Native stacktrace:

   /usr/bin/mono() [0x4b73d8]
   /usr/bin/mono() [0x50f13b]
   /usr/bin/mono() [0x423d22]
   /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7fea985a1340]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_type_check_instance+0x19) [0x7fea847b47f9]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_handlers_disconnect_matched+0x24) [0x7fea847aa5f4]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_accel_label_set_accel_closure+0xa6) [0x7fea85f24f16]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_accel_label_set_accel_widget+0xa5) [0x7fea85f25125]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x711bb) [0x7fea85f251bb]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb2) [0x7fea84792332]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x220d4) [0x7fea847a40d4]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xdd9) [0x7fea847aba29]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82) [0x7fea847abce2]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x151f90) [0x7fea86005f90]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x60) [0x7fea84798ad0]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x112db2) [0x7fea85fc6db2]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xb609f) [0x7fea85f6a09f]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb2) [0x7fea84792332]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x220d4) [0x7fea847a40d4]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xdd9) [0x7fea847aba29]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82) [0x7fea847abce2]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x151f90) [0x7fea86005f90]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x60) [0x7fea84798ad0]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x13d5e5) [0x7fea85ff15e5]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xb609f) [0x7fea85f6a09f]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb2) [0x7fea84792332]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x220d4) [0x7fea847a40d4]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xdd9) [0x7fea847aba29]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82) [0x7fea847abce2]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x151f90) [0x7fea86005f90]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x60) [0x7fea84798ad0]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x13a642) [0x7fea85fee642]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb2) [0x7fea84792332]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x220d4) [0x7fea847a40d4]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xdd9) [0x7fea847aba29]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82) [0x7fea847abce2]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x151f90) [0x7fea86005f90]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x60) [0x7fea84798ad0]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x13d5e5) [0x7fea85ff15e5]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xb609f) [0x7fea85f6a09f]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb2) [0x7fea84792332]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x220d4) [0x7fea847a40d4]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xdd9) [0x7fea847aba29]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82) [0x7fea847abce2]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x151f90) [0x7fea86005f90]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x60) [0x7fea84798ad0]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x82cfa) [0x7fea85f36cfa]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xb609f) [0x7fea85f6a09f]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb2) [0x7fea84792332]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x220d4) [0x7fea847a40d4]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xdd9) [0x7fea847aba29]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82) [0x7fea847abce2]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x151f90) [0x7fea86005f90]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x60) [0x7fea84798ad0]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xb609f) [0x7fea85f6a09f]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x138) [0x7fea847923b8]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x220d4) [0x7fea847a40d4]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xdd9) [0x7fea847aba29]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82) [0x7fea847abce2]
   /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x151f90) [0x7fea86005f90]
   /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x60) [0x7fea84798ad0]
   [0x40a3eb1b]

Debug info from gdb:

Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operación no permitida.
No threads.

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


i don't know what to do, i tried in root mode but so does. I'm using ubuntu 14.04 lts 64bit.
I hope someone can help me
gde
Newbie
 
Posts: 0
Joined: Wed Jun 10, 2015 7:38 pm

Previous

Return to PicoScope for Linux

Who is online

Users browsing this forum: No registered users and 0 guests