After update to 6.14.62-4r6350 (Linux-Mint) fails to start

Discussion forum for the Picoscope 6 Linux software
Post Reply
babr
Newbie
Posts: 0
Joined: Fri Mar 11, 2022 6:17 pm

After update to 6.14.62-4r6350 (Linux-Mint) fails to start

Post by babr »

After a recent update, Picoscope fails to startup on Linux Mint (40~20.04.1-Ubuntu)

tjozwiak
Newbie
Posts: 0
Joined: Sun Mar 13, 2022 4:56 pm

Re: After update to 6.14.62-4r6350 (Linux-Mint) fails to start

Post by tjozwiak »

The same for Ubuntu 16.04. I understand that you supported Ubuntu 18.04 but it was working really fun under 16.04 till now :(

babr
Newbie
Posts: 0
Joined: Fri Mar 11, 2022 6:17 pm

Re: After update to 6.14.62-4r6350 (Linux-Mint) fails to start

Post by babr »

As an alternative I now use the Picoscope 7 Early Access version, it works great under Linux Mint 20.3 Una

den1
Newbie
Posts: 0
Joined: Mon Mar 14, 2022 9:05 am

Re: After update to 6.14.62-4r6350 (Linux-Mint) fails to start

Post by den1 »

I have problems with Picoscope6 using Debian Bullseye.
Picoscope 7 Early Access version does not work with 2208BMSO.

I Appreciate any help.

wick1
Newbie
Posts: 0
Joined: Mon Mar 14, 2022 9:28 am

Re: After update to 6.14.62-4r6350 (Linux-Mint) fails to start

Post by wick1 »

System.TypeInitializationException: The type initializer for 'Pico.' threw an exception. ---> System.ArgumentNullException: Value cannot be null.
at Pico.Common.AppResources.GetResourceStream (System.String name, System.Boolean throwIfNull) [0x0000f] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...ctor () [0x0001d] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...cctor () [0x00000] in <691edf6ec022477fbd491cded845a01f>:0
--- End of inner exception stack trace ---
at Pico..GetDisplayName () [0x00086] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...cctor () [0x00062] in <691edf6ec022477fbd491cded845a01f>:0
--- End of inner exception stack trace ---
at Pico..Main () [0x00040] in <7095b4e4f6c449579a774296b81c2868>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'Pico.' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Pico.' threw an exception. ---> System.ArgumentNullException: Value cannot be null.
at Pico.Common.AppResources.GetResourceStream (System.String name, System.Boolean throwIfNull) [0x0000f] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...ctor () [0x0001d] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...cctor () [0x00000] in <691edf6ec022477fbd491cded845a01f>:0
--- End of inner exception stack trace ---
at Pico..GetDisplayName () [0x00086] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...cctor () [0x00062] in <691edf6ec022477fbd491cded845a01f>:0
--- End of inner exception stack trace ---
at Pico..Main () [0x00040] in <7095b4e4f6c449579a774296b81c2868>:0
-->
Mine after upgrading to 6.14.62-4r6250 also fails to start on one PC but does start with no problems on another. Both PCs are running the same OS versions and are the same models. Both Ubuntu 20.04.4 LTS and both Acer Aspire E1-570. Re-installing Picoscope does no fix the problem. It makes no difference if my picoscope 2204A unit is plugged in or not. I see no problems with other software on the non starting PC.
Clicking on the Picoscope icon produces only the text "Picoscope 6" in the bar at the top of the screen.
After typing picoscope at the command line, the linux prompt immediately reappears with no messages.
I include the output below produced after typing the command:-
mono /opt/picoscope/lib/PicoScope.GTK.exe
The "Failed to load module" message seems irrelevant here as this also appears on the PC where pico does start with no problems. I imagine the "Exception" messages are a clue but I don't understand how to analyse these.
Following the above commands, no trace file or any other information appears in
/home/.local/share/Pico Technology

Any advice on how to diagnose would be greatly appreciated.
-----------------------------------------------------------------------------------------------------------------------------------------
$ mono /opt/picoscope/lib/PicoScope.GTK.exe
Gtk-Message: 17:56:15.315: Failed to load module "canberra-gtk-module"

Unhandled Exception:
System.TypeInitializationException: The type initializer for 'Pico.' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Pico.' threw an exception. ---> System.ArgumentNullException: Value cannot be null.
at Pico.Common.AppResources.GetResourceStream (System.String name, System.Boolean throwIfNull) [0x0000f] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...ctor () [0x0001d] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...cctor () [0x00000] in <691edf6ec022477fbd491cded845a01f>:0
--- End of inner exception stack trace ---
at Pico..GetDisplayName () [0x00086] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...cctor () [0x00062] in <691edf6ec022477fbd491cded845a01f>:0
--- End of inner exception stack trace ---
at Pico..Main () [0x00040] in <7095b4e4f6c449579a774296b81c2868>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'Pico.' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Pico.' threw an exception. ---> System.ArgumentNullException: Value cannot be null.
at Pico.Common.AppResources.GetResourceStream (System.String name, System.Boolean throwIfNull) [0x0000f] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...ctor () [0x0001d] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...cctor () [0x00000] in <691edf6ec022477fbd491cded845a01f>:0
--- End of inner exception stack trace ---
at Pico..GetDisplayName () [0x00086] in <691edf6ec022477fbd491cded845a01f>:0
at Pico...cctor () [0x00062] in <691edf6ec022477fbd491cded845a01f>:0
--- End of inner exception stack trace ---
at Pico..Main () [0x00040] in <7095b4e4f6c449579a774296b81c2868>:0