[svxlink-devel] what version of Qt to use?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[svxlink-devel] what version of Qt to use?

Rob Janssen
I downloaded the latest svxlink and tried to compile it.
When I use qtel, the terminal window where I started it shows a lot of these errors:

QObject: Do not delete object, 'unnamed', during its event handler!
Sometimes during transmit, it displays:
QObject::startTimer: QTimer cannot have a negative interval
and briefly switches back to receive.

It also randomly crashes, apparently when the connection is closed by the remote.
I wonder if I may be using an incorrect version of Qt.

My Qt library is version 4.4.3
What version does qtel expect?  Are statically linked (with the proper Qt library)
binary versions available somewhere?

73,
Rob

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|

Re: what version of Qt to use?

Tobias Blomberg
On Tuesday 21 January 2014 23:13:24 Rob Janssen wrote:
> I downloaded the latest svxlink and tried to compile it.
> When I use qtel, the terminal window where I started it shows a lot of these
> errors:
>
> QObject: Do not delete object, 'unnamed', during its event handler!
> Sometimes during transmit, it displays:
> QObject::startTimer: QTimer cannot have a negative interval
> and briefly switches back to receive.

I get none of these on my system (Manjaro Linux with Qt 4.8.5). Anyone else
seen this?


> It also randomly crashes, apparently when the connection is closed by the
> remote. I wonder if I may be using an incorrect version of Qt.
>
> My Qt library is version 4.4.3
> What version does qtel expect?  Are statically linked (with the proper Qt
> library) binary versions available somewhere?

I'm not sure what lowest version of Qt that can be used but I'd guess you
could use a pretty old one without problems. On my CentOS 5 system it's Qt
4.2.2 and it compiles without problems. I also tested it quickly and it showed
none of the error messages above.

What distribution are you using?
May there be any old svxlink libraries on your system from an old
installation?
Try to run qtel directly from the source tree after a recompilation:

make distclean
make
export LD_LIBRARY_PATH=$(pwd)/lib
bin/qtel

73's de SM0SVX / Tobias

>
> 73,
> Rob


------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|

Re: what version of Qt to use?

Rob Janssen
SM0SVX wrote:
> I'm not sure what lowest version of Qt that can be used but I'd guess you
> could use a pretty old one without problems. On my CentOS 5 system it's Qt
> 4.2.2 and it compiles without problems. I also tested it quickly and it showed
> none of the error messages above.
>
> What distribution are you using?
My system is running openSUSE 11.1
Old...  I know.   I should update soon.  Already made some preparations for that.
It is 64-bit, maybe that matters too.
I installed all libraries from the distribution and in fact I installed the "development" packages
for some of them especially for this compile, as I had only the runtime libraries installed.
> May there be any old svxlink libraries on your system from an old
> installation?
No, it was my first attempt to use your software.  I unpacked it in a user directory, did
a make and then a make install from a root shell.
$ which qtel
/usr/bin/qtel
$ ldd /usr/bin/qtel
         linux-vdso.so.1 =>  (0x00007fff5c1ff000)
         libecholib.so.1.2 => /usr/lib/libecholib.so.1.2 (0x00007fd08c57e000)
         libasyncqt.so.1.2 => /usr/lib/libasyncqt.so.1.2 (0x00007fd08c362000)
         libasyncaudio.so.1.2 => /usr/lib/libasyncaudio.so.1.2 (0x00007fd08c0e8000)
         libasynccore.so.1.2 => /usr/lib/libasynccore.so.1.2 (0x00007fd08be87000)
         libQtGui.so.4 => /usr/lib64/libQtGui.so.4 (0x00007fd08b372000)
         libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x00007fd08b14a000)
         libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007fd08af41000)
         libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007fd08ad24000)
         libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007fd08ab1a000)
         libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fd08a910000)
         libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007fd08a708000)
         libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007fd08a502000)
         libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007fd08a2f7000)
         libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007fd08a0f4000)
         libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fd089e6f000)
         libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007fd089c3d000)
         libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fd089a2b000)
         libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fd0896ee000)
         libQtNetwork.so.4 => /usr/lib64/libQtNetwork.so.4 (0x00007fd0893eb000)
         libQtCore.so.4 => /usr/lib64/libQtCore.so.4 (0x00007fd088fbe000)
         libz.so.1 => /lib64/libz.so.1 (0x00007fd088da8000)
         libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007fd088ba3000)
         librt.so.1 => /lib64/librt.so.1 (0x00007fd08899a000)
         libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007fd0886d5000)
         libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd0884b9000)
         libdl.so.2 => /lib64/libdl.so.2 (0x00007fd0882b5000)
         libsigc-2.0.so.0 => /usr/lib64/libsigc-2.0.so.0 (0x00007fd0880af000)
         libgsm.so.1 => /usr/lib64/libgsm.so.1 (0x00007fd087ea3000)
         libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fd087b97000)
         libm.so.6 => /lib64/libm.so.6 (0x00007fd087941000)
         libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fd087729000)
         libc.so.6 => /lib64/libc.so.6 (0x00007fd0873d0000)
         libspeex.so.1 => /usr/lib64/libspeex.so.1 (0x00007fd0871b6000)
         libasound.so.2 => /usr/lib64/libasound.so.2 (0x00007fd086ee6000)
         libuuid.so.1 => /lib64/libuuid.so.1 (0x00007fd086ce1000)
         libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fd086ab7000)
         libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fd0868b3000)
         libxcb-xlib.so.0 => /usr/lib64/libxcb-xlib.so.0 (0x00007fd0866b1000)
         libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fd086495000)
         libpcre.so.0 => /usr/lib64/libpcre.so.0 (0x00007fd086265000)
         /lib64/ld-linux-x86-64.so.2 (0x00007fd08c7e3000)
$ locate qtel | grep 'qtel$'
/local/home/rob/svxlink-13.12/bin/qtel
/local/home/rob/svxlink-13.12/qtel
/usr/bin/qtel
/usr/share/qtel

> Try to run qtel directly from the source tree after a recompilation:
>
> make distclean
> make
> export LD_LIBRARY_PATH=$(pwd)/lib
> bin/qtel
>
>
Result is the same...
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
Switching to SPEEX audio codec for EchoLink Qso.
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!

Here I disconnected about 5 seconds after connecting, normally those messages
would continue and sooner or later the program would cause "Segmentation Fault".
However, while it is working, it works fine.  Receive and transmit without problem.

Thanks for your reply!  I'll see what I can do to locate this problem.

73,
Rob

------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|

Re: what version of Qt to use?

Tobias Blomberg
I'd say upgrading your OS probably is the easiest way to solve the problem.
Since you were going to do that anyway I'd put the time on that instead of
looking for the specific problem with Qtel.

Now you have a reason to do the upgrade :-)

73's de SM0SVX / Tobias


On Saturday 01 February 2014 10:26:56 Rob Janssen wrote:

> SM0SVX wrote:
> > I'm not sure what lowest version of Qt that can be used but I'd guess you
> > could use a pretty old one without problems. On my CentOS 5 system it's Qt
> > 4.2.2 and it compiles without problems. I also tested it quickly and it
> > showed none of the error messages above.
> >
> > What distribution are you using?
>
> My system is running openSUSE 11.1
> Old...  I know.   I should update soon.  Already made some preparations for
> that. It is 64-bit, maybe that matters too.
> I installed all libraries from the distribution and in fact I installed the
> "development" packages for some of them especially for this compile, as I
> had only the runtime libraries installed.
> > May there be any old svxlink libraries on your system from an old
> > installation?
>
> No, it was my first attempt to use your software.  I unpacked it in a user
> directory, did a make and then a make install from a root shell.
> $ which qtel
> /usr/bin/qtel
> $ ldd /usr/bin/qtel
>          linux-vdso.so.1 =>  (0x00007fff5c1ff000)
>          libecholib.so.1.2 => /usr/lib/libecholib.so.1.2
> (0x00007fd08c57e000) libasyncqt.so.1.2 => /usr/lib/libasyncqt.so.1.2
> (0x00007fd08c362000) libasyncaudio.so.1.2 => /usr/lib/libasyncaudio.so.1.2
> (0x00007fd08c0e8000) libasynccore.so.1.2 => /usr/lib/libasynccore.so.1.2
> (0x00007fd08be87000) libQtGui.so.4 => /usr/lib64/libQtGui.so.4
> (0x00007fd08b372000) libpng12.so.0 => /usr/lib64/libpng12.so.0
> (0x00007fd08b14a000) libSM.so.6 => /usr/lib64/libSM.so.6
> (0x00007fd08af41000)
>          libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007fd08ad24000)
>          libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007fd08ab1a000)
>          libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fd08a910000)
>          libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007fd08a708000)
>          libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007fd08a502000)
>          libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007fd08a2f7000)
>          libXinerama.so.1 => /usr/lib64/libXinerama.so.1
> (0x00007fd08a0f4000) libfreetype.so.6 => /usr/lib64/libfreetype.so.6
> (0x00007fd089e6f000) libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1
> (0x00007fd089c3d000) libXext.so.6 => /usr/lib64/libXext.so.6
> (0x00007fd089a2b000) libX11.so.6 => /usr/lib64/libX11.so.6
> (0x00007fd0896ee000) libQtNetwork.so.4 => /usr/lib64/libQtNetwork.so.4
> (0x00007fd0893eb000) libQtCore.so.4 => /usr/lib64/libQtCore.so.4
> (0x00007fd088fbe000) libz.so.1 => /lib64/libz.so.1 (0x00007fd088da8000)
>          libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0
> (0x00007fd088ba3000) librt.so.1 => /lib64/librt.so.1 (0x00007fd08899a000)
>          libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0
> (0x00007fd0886d5000) libpthread.so.0 => /lib64/libpthread.so.0
> (0x00007fd0884b9000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fd0882b5000)
>          libsigc-2.0.so.0 => /usr/lib64/libsigc-2.0.so.0
> (0x00007fd0880af000) libgsm.so.1 => /usr/lib64/libgsm.so.1
> (0x00007fd087ea3000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6
> (0x00007fd087b97000) libm.so.6 => /lib64/libm.so.6 (0x00007fd087941000)
>          libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fd087729000)
>          libc.so.6 => /lib64/libc.so.6 (0x00007fd0873d0000)
>          libspeex.so.1 => /usr/lib64/libspeex.so.1 (0x00007fd0871b6000)
>          libasound.so.2 => /usr/lib64/libasound.so.2 (0x00007fd086ee6000)
>          libuuid.so.1 => /lib64/libuuid.so.1 (0x00007fd086ce1000)
>          libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fd086ab7000)
>          libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fd0868b3000)
>          libxcb-xlib.so.0 => /usr/lib64/libxcb-xlib.so.0
> (0x00007fd0866b1000) libxcb.so.1 => /usr/lib64/libxcb.so.1
> (0x00007fd086495000) libpcre.so.0 => /usr/lib64/libpcre.so.0
> (0x00007fd086265000) /lib64/ld-linux-x86-64.so.2 (0x00007fd08c7e3000)
> $ locate qtel | grep 'qtel$'
> /local/home/rob/svxlink-13.12/bin/qtel
> /local/home/rob/svxlink-13.12/qtel
> /usr/bin/qtel
> /usr/share/qtel
>
> > Try to run qtel directly from the source tree after a recompilation:
> >
> > make distclean
> > make
> > export LD_LIBRARY_PATH=$(pwd)/lib
> > bin/qtel
>
> Result is the same...
> QObject: Do not delete object, 'unnamed', during its event handler!
> QObject: Do not delete object, 'unnamed', during its event handler!
> QObject: Do not delete object, 'unnamed', during its event handler!
> QObject: Do not delete object, 'unnamed', during its event handler!
> QObject: Do not delete object, 'unnamed', during its event handler!
> Switching to SPEEX audio codec for EchoLink Qso.
> QObject: Do not delete object, 'unnamed', during its event handler!
> QObject: Do not delete object, 'unnamed', during its event handler!
>
> Here I disconnected about 5 seconds after connecting, normally those
> messages would continue and sooner or later the program would cause
> "Segmentation Fault". However, while it is working, it works fine.  Receive
> and transmit without problem.
>
> Thanks for your reply!  I'll see what I can do to locate this problem.
>
> 73,
> Rob


------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|

Re: what version of Qt to use?

Rob Janssen
This weekend I finally upgraded the system to openSUSE 13.1, and although there of
course are a lot of new issues and many things to do before it is running as well as before,
this problem with Qtel is now gone!  The messages no longer appear and it does not crash.

Rob

SM0SVX wrote:
> I'd say upgrading your OS probably is the easiest way to solve the problem.
> Since you were going to do that anyway I'd put the time on that instead of
> looking for the specific problem with Qtel.
>
> Now you have a reason to do the upgrade :-)
>
> 73's de SM0SVX / Tobias
>


------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel