Re: [Svxlink-devel] QTel does not return to standby mode
Brought to you by:
sm0svx
From: Tobias B. <sm...@us...> - 2013-03-28 13:12:33
|
Hi Volodymyr, The "100% CPU load after incoming connect" bug in Qtel should now be resolved in Subversion trunk. 73's de SM0SVX / Tobias On 03/18/2013 12:36 AM, Volodymyr wrote: > 17.03.2013 23:02, Tobias Blomberg пишет: >> On 03/11/2013 11:30 PM, Volodymyr wrote: >>> 08.03.2013 22:32, Tobias Blomberg пишет: >>>> On 03/08/2013 09:22 PM, Volodymyr wrote: >>>>> Hello Tobias, >>>>> >>>>> I'm sorry. >>>>> >>>>> Just checked. >>>>> Removed, the audio file, the error is still present. >>>>> >>>>> If Qtel connected to the conference. >>>>> When receiving audio packets, everything works fine. >>>>> When the reception is over - load on the CPU cycles increases to 80%. >>>> OK. Thanks for the feed-back. >>>> >>>> 73's de SM0SVX / Tobias >>> Today checked installation for Debian 6. >>> >>> Everything works. >>> >>> But when working Qtel, always get the message: >>> >>> volodymyr@debian:~$ qtel >>> QObject::startTimer: QTimer cannot have a negative interval >>> QObject::startTimer: QTimer cannot have a negative interval >>> QObject::startTimer: QTimer cannot have a negative interval >> Now that's strange. Never seen it before. Was this on a newly installed >> system or is it possible you had some old Qtel config in your homedir? > The newly installed Debian 6.0.7 > Gnome desktop 2.30 > libqt4-dev 4.6.3 > Old config - no. > > Message appears at the end of the regime "RX". > When the green indicator "RX" - light off, this message appears. > > Regards, > Volodymyr > > |