** Changed in: libgtop
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used by system monitor reporting incorrect number of
processors
libgtop2 2.32.0 included in Ubuntu 16.04 LTS has bumped the CPU number
limit to 1024.
Therefore, I'm closing this bug since that is more than this bug
originally asked for and I'm skeptical whether tools using libgtop2 can
adequately work with more than 1024 CPUs anyway.
** Changed in: libgtop2
This is still an issue for 16.04 and an 80 "core" system. SysInfo only
shows 72 cores while lscpu shows 80. As an aside the layout of the
SysInfo GUI could do with a workover. For 4 CPUs it is fine but after
that it starts to get very red. I have 3 machines with dual hexacores
and 2 machines with
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as Won't Fix.
** Changed in: libgtop2 (Ubuntu Saucy)
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package libgtop2 - 2.30.0.is.2.30.0-0ubuntu1
---
libgtop2 (2.30.0.is.2.30.0-0ubuntu1) utopic; urgency=medium
* New upstream release
- Increases maximum CPU limit (LP: #1210280)
* debian/control:
* debian/rules:
* debian/libgtop2-10.install
*
** Changed in: libgtop2 (Ubuntu)
Status: Fix Released = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used by system monitor reporting incorrect number of
** Branch linked: lp:ubuntu/utopic-proposed/libgtop2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used by system monitor reporting incorrect number of
processors for
I incorrectly marked libgtop2 2.30.0.is.2.30.0-0ubuntu1 as fixing this
bug. I doesn't so please mark it back from Fix Committed when that
version lands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** No longer affects: lansing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used by system monitor reporting incorrect number of
processors for Ubuntu 13.10 vms on Hyper-V
** Changed in: lansing
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used by system monitor reporting incorrect number of
processors
Note that this patch breaks the ABI according to upstream, so this needs
to go along with a SONAME bump and a library transition. Bumping the
SONAME in a distro specific patch is absolutely nothing that we want to
do, so this ought to be applied/fixed upstream, SONAME bumped there, and
released as
** Changed in: libgtop
Status: Unknown = Confirmed
** Changed in: libgtop
Importance: Unknown = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used by
Apparently SuSE has patched there version (and is likely that disconnect
is what triggered the initial customer concern.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used
** Changed in: lansing
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used by system monitor reporting incorrect number of
processors for
Thanks for the debdiff, but:
1- Won't changing GLIBTOP_NCPU break ABI, and require a bunch of other packages
to be rebuilt?
2- Won't increasing GLIBTOP_NCPU dramatically increase memory consumption?
** Bug watch added: GNOME Bug Tracker #323354
Marc,
I didn't see that GLIBTOP_NCPU was used anywhere else. I'll dig some more.
Yes, it will dramatically increase memory consumption in some tools.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The attachment Change GLIBTOP_NCPU from 32 to 256 seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the patch flag from the
attachment, remove the patch
** Changed in: libgtop2 (Ubuntu)
Status: New = Triaged
** Changed in: libgtop2 (Ubuntu)
Importance: Undecided = Medium
** Also affects: libgtop2 (Ubuntu Saucy)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- System monitor reporting incorrect number of processors for Ubuntu 13.10 vms
on Hyper-V
+ libgtop2 used by system monitor reporting incorrect number of processors for
Ubuntu 13.10 vms on Hyper-V
--
You received this bug notification because you are a member of Ubuntu
** Patch added: Change GLIBTOP_NCPU from 32 to 256
https://bugs.launchpad.net/ubuntu/+source/libgtop2/+bug/1210280/+attachment/3771706/+files/libgtop2.lp1210280.patch
** Changed in: lansing
Milestone: None = ubuntu-13.08.31
--
You received this bug notification because you are a member
20 matches
Mail list logo
