Re: [wsjt-devel] WSPR SegFault on Decode

2016-02-08 Thread Russ Woodman
Greg, 

I installed them as needed out of the Debian repos. I didn't use the JDK 
because I didn't know about it until after I did the build. It looks like it 
only provides hamlib3 support? Are there some versions I should compare between 
my system libraries and the JDK? 

73, Russ - K5TUX 

- Original Message -

From: "KI7MT" <ki...@yahoo.com> 
To: wsjt-devel@lists.sourceforge.net 
Sent: Monday, February 8, 2016 11:01:58 AM 
Subject: Re: [wsjt-devel] WSPR SegFault on Decode 

Hi Russ, 

I'm assuming you are comping from source here. How did you install the 
build and runtime package dependencies for WSPR? 

73's 
Greg 



On 02/08/2016 08:55 AM, Russ Woodman wrote: 
> Hi, 
> 
> Just built WSPR 4.0r6470 from the SVN on my Linux machine running Debian 
> Jessie. I can start the application and configure it with no problems. Rig 
> control is working. During the receive cycle, WSPR operates correctly. When 
> it goes to decode the received data, it segfaults. Here is what I see in my 
> start-up terminal window: 
> 
> -- 
> RUNNING WSPR 
> -- 
> 
> Instance Name ..: WSPR 
> Script Name : /usr/local/bin/wspr 
> Run Directory ..: /home/russ/.local/share/WSPR 
> 
> *** 
> WSPR Version 4.0 r6470, by K1JT 
> Revision date ...: 2016-01-12 01:54:47 -0700 (Tue, 12 Jan 2016) 
> Run date : Mon Feb 8 15:41:27 2016 UTC 
> ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear 
> ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_life 
> ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side 
> ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map 
> ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map 
> /usr/local/bin/wspr: line 225: 2994 Segmentation fault env 
> PYTHONPATH=/usr/local/lib/wspr /usr/bin/python3 -O 
> /usr/local/share/wspr/wspr.py 
> 
> The ALSA messages are before the decode cycle. The last error line is where 
> the problem occurs. Any thoughts? 
> 
> 73, Russ - K5TUX 

-- 
Site24x7 APM Insight: Get Deep Visibility into Application Performance 
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month 
Monitor end-to-end web transactions and take corrective actions now 
Troubleshoot faster and improve end-user experience. Signup Now! 
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140 
___ 
wsjt-devel mailing list 
wsjt-devel@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel 

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSPR SegFault on Decode

2016-02-08 Thread Russ Woodman
Greg, 

I read through the special information you provided below. I removed the 
python3-pil and python3-pil.imagetk packages from my system and built them 
using the procedure outlined in the docs. Apparently that was the trouble as 
WSPR is now fully functional and my spots are showing up on the map. Thanks for 
the help. 

73, Russ - K5TUX 

- Original Message -

From: "KI7MT" <ki...@yahoo.com> 
To: wsjt-devel@lists.sourceforge.net 
Sent: Monday, February 8, 2016 12:34:10 PM 
Subject: Re: [wsjt-devel] WSPR SegFault on Decode 

Hi Russ, 

There is no pressing need to use JTSDK to build WSJT, WSPR or WSJT-X on 
Linux. All of the apps can be built natively provided the build and 
runtime dependencies have been met. WSJT-X has a special requirement of 
passing a locally built version of Hamlib3, but that is easy enough to 
deal with when following the build instructions included in the 
repository checkout. 

As a side note, WSJT-X now provides WSPR, and it has an much improved 
decoder. You may want to consider using WSJT-X >> WSPR rather than the 
older Python3 version, but that's up to you. 

For WSJT and WSPR on Debian Jessie (v8.0), there is a package 
incompatibility issue that is unfortunate, but it is what it is. 

The first thing is to ensure you have the build environment set-up 
correctly. For this, you can use the instructions for JTSDK to install 
and configure and install build dependencies (this will not install JTSDK): 

https://sourceforge.net/p/jtsdk/jtsdk/HEAD/tree/jtsdk-nix/trunk/README.pkg-lists
 

See Section: SPECIAL: Ubuntu 14.10 (Utopic) and Debian 8.x (Jessie) 

Obviously, if you are only concerned with the Python3 version of WSPR, 
you would not need cmake, clang, or any the QT packages. 

After your certain you have set-up the Python3 packaging correctly, 
re-build / re-run WSPR to test the status of things. 


73's 
Greg, KI7MT 




On 02/08/2016 11:09 AM, Russ Woodman wrote: 
> Greg, 
> 
> I installed them as needed out of the Debian repos. I didn't use the JDK 
> because I didn't know about it until after I did the build. It looks like it 
> only provides hamlib3 support? Are there some versions I should compare 
> between my system libraries and the JDK? 
> 
> 73, Russ - K5TUX 
> 
> - Original Message - 
> 
> From: "KI7MT" <ki...@yahoo.com> 
> To: wsjt-devel@lists.sourceforge.net 
> Sent: Monday, February 8, 2016 11:01:58 AM 
> Subject: Re: [wsjt-devel] WSPR SegFault on Decode 
> 
> Hi Russ, 
> 
> I'm assuming you are comping from source here. How did you install the 
> build and runtime package dependencies for WSPR? 
> 
> 73's 
> Greg 
> 
> 
> 
> On 02/08/2016 08:55 AM, Russ Woodman wrote: 
>> Hi, 
>> 
>> Just built WSPR 4.0r6470 from the SVN on my Linux machine running Debian 
>> Jessie. I can start the application and configure it with no problems. Rig 
>> control is working. During the receive cycle, WSPR operates correctly. When 
>> it goes to decode the received data, it segfaults. Here is what I see in my 
>> start-up terminal window: 
>> 
>> -- 
>> RUNNING WSPR 
>> -- 
>> 
>> Instance Name ..: WSPR 
>> Script Name : /usr/local/bin/wspr 
>> Run Directory ..: /home/russ/.local/share/WSPR 
>> 
>> *** 
>> WSPR Version 4.0 r6470, by K1JT 
>> Revision date ...: 2016-01-12 01:54:47 -0700 (Tue, 12 Jan 2016) 
>> Run date : Mon Feb 8 15:41:27 2016 UTC 
>> ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear 
>> ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM 
>> cards.pcm.center_life 
>> ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side 
>> ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map 
>> ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map 
>> /usr/local/bin/wspr: line 225: 2994 Segmentation fault env 
>> PYTHONPATH=/usr/local/lib/wspr /usr/bin/python3 -O 
>> /usr/local/share/wspr/wspr.py 
>> 
>> The ALSA messages are before the decode cycle. The last error line is where 
>> the problem occurs. Any thoughts? 
>> 
>> 73, Russ - K5TUX 
> 
> --
>  
> Site24x7 APM Insight: Get Deep Visibility into Application Performance 
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month 
> Monitor end-to-end web transactions and take corrective actions now 
> Troubleshoot faster and improve end-user experience. Signup Now! 
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4