ubuntu-hams-devel team mailing list archive

[David Aitcheson - KB3EFS <454740@xxxxxxxxxxxxxxxxxx>]

Gentlemen,

Please kindly direct all future bug complaints to
Xastir@xxxxxxxxxxxxxxxx

The developers are always active on that Mailman List-serve.

Additionally this may have been fixed in a later release, the current
release is V2.0.9 built from source on GitHub and works FB for me.

You are addressing V1.9.4-3 which is known to have had issues that are
most definitely fixed in more recent versions.

My suggestion to you both is to subscribe to Xastir@xxxxxxxxxxxxxxxx via
http://xastir.org/mailman/listinfo/xastir and join the discussion.

Very 73,
Dave - KB3EFS


On 11/07/2016 11:05 AM, Kevin Otte wrote:
> Might as well. When upstream says "Well no one else is complaining"
> you're not likely to get anywhere. Just because CPUs have gotten
> faster doesn't mean the problem has gone away, only masked.

-- 
You received this bug notification because you are a member of Ubuntu
ham developers, which is subscribed to xastir in Ubuntu.
https://bugs.launchpad.net/bugs/454740

Title:
  xastir consumes CPU time in X11 socket I/O

Status in xastir:
  Unknown
Status in xastir package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: xastir

  kjotte@zarya:~$ lsb_release -rd
  Description:	Ubuntu 9.04
  Release:	9.04

  kjotte@zarya:~$ apt-cache policy xastir
  xastir:
    Installed: 1.9.4-3
    Candidate: 1.9.4-3
    Version table:
   *** 1.9.4-3 0
          500 http://archive.linux.duke.edu jaunty/universe Packages
          100 /var/lib/dpkg/status

  After upgrading from Intrepid (xastir 1.9.2) to Jaunty I noticed my
  CPU was running at a constant ~10%.  Running an strace revealed there
  was quite a bit time spent timing out of polls on the X11 socket fd.
  I tried setting the DISPLAY to use TCP instead of UNIX sockets, but
  the high poll activity still occurred.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xastir/+bug/454740/+subscriptions