** Branch linked: lp:~ubuntu-desktop/gnome-system-monitor/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919014
Title:
gnome-system-monitor crashed with SIGABRT in __libc_message()
To manage
This bug was fixed in the package gnome-system-monitor - 3.3.90-0ubuntu1
---
gnome-system-monitor (3.3.90-0ubuntu1) precise; urgency=low
* New upstream release.
- Hide kthreadd by default (LP: #406825)
- Fix crash if default colors list is shorter than the number of CPUs.
manual solution with dconf have done it
manually add all (core_number,'#FF') fix also this crash on my side... but
have to do it for all 12 cores (intel i7 3930)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-system-monitor
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919014
Title:
gnome-system-monitor crashed with SIGABRT in
** Changed in: gnome-system-monitor (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919014
Title:
gnome-system-monitor crashed with SIGABRT in
thanks rober roth your fix worked on my 8 core =)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919014
Title:
gnome-system-monitor crashed with SIGABRT in __libc_message()
To manage notifications
** Changed in: gnome-system-monitor
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919014
Title:
gnome-system-monitor crashed with SIGABRT in __libc_message()
To
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege
