I built the trustedqsl package with 'nostrip' and ran it from gdb.
The segfault appears to be in the wxwidgets code.
I've emailed the wxwidgets maintainer team.
Colin
--
Colin Tuckley | +44(0)1223 830814 | PGP/GnuPG Key Id
Debian Developer | +44(0)7799 143369 | 0x38C9D903
--
* On 2014 24 Sep 10:11 -0500, Colin Tuckley wrote:
I built the trustedqsl package with 'nostrip' and ran it from gdb.
The segfault appears to be in the wxwidgets code.
I've emailed the wxwidgets maintainer team.
Did you notice that in some dialogs the buttons are shrunk to only a few
Package: trustedqsl
Followup-For: Bug #759224
Dear Maintainer,
I built trustedqsl from the 2.0.3 source, the 02-wx3.0-compat.patch file in
trustedqsl_2.0.2b-1.debian.tar.xz applied cleanly and I found the segfault
still
exists in this version.
Thanks to snapshot.debian.org I was able to
Package: trustedqsl
Version: 2.0.2b-1
Followup-For: Bug #759224
Dear Maintainer,
I too am seeing the segmentation fault when attempting to create a
new location under a special event callsign I already had registered
tqsl several years ago. When I first started tqsl I received a pop-up
that a
Package: trustedqsl
Version: 2.0.2b-1
Followup-For: Bug #759224
For John and anyone else. I found that I had previously requested a new
certificate for each year I used the special event 1x1 callsign. I have
now done that for this year's operation and limited the dates in the
certificate
Package: trustedqsl
Version: 2.0.2-2
Severity: important
I have been using older versions of tqsl for some time, but when I try
to add a new special event callsign to this one -- I do have my cert
from LOTW imported -- I can't add a station location. It segfaults
immediately every time. Same if
6 matches
Mail list logo
