Upstream doesn't care. Closing this out to clean up my bug list.
** Changed in: xastir (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/454740
Title:
xastir
Gentlemen,
Please kindly direct all future bug complaints to
xas...@lists.xastir.org
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
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
Bugs, which is subscribed to
so could we close it now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/454740
Title:
xastir consumes CPU time in X11 socket I/O
To manage notifications about this bug go to:
Going back through old bug reports and stumbled across this still open.
Fired up xastir on my ham box to check it out.
Machine I'm running it on is significantly newer, but I am indeed still
seeing about an 8% CPU load from the xastir 2.0.6 process on Ubuntu
15.10. I strace'd the running process
Kevin, Iain, Kamal, et al,
_ALL_ Xastir bugs and problems are handled on/at
xas...@lists.xastir.org.
ALL support is to be routed via that reflector.
The CPU load you are seeing is normal for all operating systems as far
as I know.
Many are now running Xastir on headless Raspbery-Pi's without
Last activity on this bug was 2010. Can anyone say if this is still an
issue in version 2.0.6?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/454740
Title:
xastir consumes CPU time in X11 socket I/O
** Changed in: xastir (Ubuntu)
Importance: Undecided = Low
** Changed in: xastir (Ubuntu)
Status: Confirmed = Triaged
--
xastir consumes CPU time in X11 socket I/O
https://bugs.launchpad.net/bugs/454740
You received this bug notification because you are a member of Ubuntu
Bugs, which
Reported the bug against xastir-1.9.6 to the project home at
SourceForge; added bug watch.
** Bug watch added: SourceForge.net Tracker #2928969
http://sourceforge.net/support/tracker.php?aid=2928969
** Also affects: xastir via
http://sourceforge.net/support/tracker.php?aid=2928969
** Changed in: xastir (Ubuntu)
Status: Confirmed = In Progress
** Changed in: xastir (Ubuntu)
Assignee: (unassigned) = Kamal Mostafa (kamalmostafa)
--
xastir consumes CPU time in X11 socket I/O
https://bugs.launchpad.net/bugs/454740
You received this bug notification because you are
** Changed in: xastir (Ubuntu)
Status: New = Confirmed
--
xastir consumes CPU time in X11 socket I/O
https://bugs.launchpad.net/bugs/454740
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The problem still occurs in the latest upstream version xastir-1.9.6 (
available for testing in my PPA:
https://launchpad.net/~kamalmostafa/+archive/xastir ).
Strace on xastir-1.9.6 shows this sequence spinning hard:
sched_yield() = 0
sched_yield()
** Attachment added: short run of strace showing heavy activity on fd 3
http://launchpadlibrarian.net/33905111/xastir-fd3-strace.txt
--
xastir consumes CPU time in X11 socket I/O
https://bugs.launchpad.net/bugs/454740
You received this bug notification because you are a member of Ubuntu
13 matches
Mail list logo
