[Elecraft] K3 update issues on Linux

[Mike Clarke]

I created it manually before unpacking the tarball into it.  It's
owned by my normal login user -- the same user I was running k3util as
-- and the directory permissions are 755.

Thanks,

-- 
Mike, M0PRL

On Sun, May 3, 2009 at 9:30 PM, Kevin <rkstover at mchsi.com> wrote:
> Who made the Elecraft folder and what permissions are assigned to it?
>
> Mike Clarke wrote:
>>
>> On Fri, May 1, 2009 at 12:23 AM, Mike Clarke <clarkema at gmail.com> wrote:
>>
>>
>>>
>>> Hi,
>>>
>>> I'm trying to update my K3 using the firmware utility on Linux (Debian
>>> Lenny.)
>>>
>>
>> [snip]
>>
>>
>>>
>>> As a result, the downloaded files are saved in $HOME/Elecraft, rather
>>> than $HOME/Elecraft/K3_Firmware, and it seems the firmware updater
>>> doesn't detect them.  I tried:
>>>
>>> $ cd ~ ; rm -rf Elecraft ; mkdir Elecraft
>>> $ tar -zxvf k3utility.tgz -C Elecraft
>>> $ cd Elecraft
>>> $ mkdir K3_Firmware
>>>
>>> and then tried the update again.  This time, the files are downloaded
>>> without complaint, and stored in $HOME/Elecraft/K3_Firmware.
>>>
>>> However, when the download is complete, I get an error dialog: "An
>>> exception of class NilObjectException was not handled.  The
>>> application must shut down."
>>>
>>
>> An off-list reply from David, W4SMT, prompted some further checks.  If I
>> unpack
>> the original tarball into ~/foo instead of ~/Elecraft, it all seems to
>> work correctly;
>> I can download updated firmware from Elecraft, and the utility offers
>> to allow me
>> to update my rig.
>>
>> The problem _seems_ be caused by my random selection of ~/Elecraft as a
>> directory to unpack the tarball into.  It seems that, because that
>> directory
>> already existed when k3util was first run, it didn't create
>> ~/Elecraft/K3_Firmware
>> as it did when I unpacked into ~/foo.  Possibly a bug in k3util, or I
>> have missed
>> something?
>>
>> Thanks,
>>
>>
>
>