I cant test it on Ubuntu Precise Pangolin, but it doesn't matter, it
would be a lot of people who would like to continue using 11.10,
moreover what if bug is not fixed? We have to wait more? I can confirm
I'm using 3.2.1 and bug still presents
--
You received this bug notification because you
@DarkMind (ipsissimus): If it's Fixed in Precise Pangolin, then the bug is
fixed in the latest version of the package. In that case it is possible to
backport the fix to an earlier release, like Oneiric (11.10) (if it is regarded
as important enough). However if it's not fixed in the latest
What kind of response are you looking for, bug still exists.
System Monitor closes if you dont look at the tabs, if you change the tabs from
System to Processes tab then it is not closing, and you have to force close it
--
You received this bug notification because you are a member of Ubuntu
DarkMind (ipsissimus): See the previous question in comment 18. I just
wanted to know whether anyone still has this using System Monitor 3.4.0
from Precise, as there have been lots of changes and improvements in
System Monitor in this cycle, and some were to address long closing
time. Which
As there has been no response in the last two months to the question
from comment 18, I am closing this bug as Invalid. Feel free to reopen
by setting the status to Confirmed if you still experience the behavior.
** Changed in: gnome-system-monitor (Ubuntu)
Status: Incomplete = Invalid
--
** Changed in: gnome-system-monitor (Ubuntu)
Assignee: Robert Roth (evfool) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/482680
Title:
System
Could anyone affected try if this is still the case with GNOME system
monitor from the current development version of Ubuntu Precise Pangolin?
This might have been fixed upstream.
** Changed in: gnome-system-monitor (Ubuntu)
Status: Confirmed = Incomplete
** Changed in:
This could be related to an upstream issue [1], seemingly fixed in the 3.3.2
development release.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=655964
** Bug watch added: GNOME Bug Tracker #655964
https://bugzilla.gnome.org/show_bug.cgi?id=655964
--
You received this bug notification
I can confirm this issue on Ubuntu 11.10 (upgraded from 10.04). I am not
able to close gnome-system-monitor the usual way by clicking on the red
cross in the top left corner, I have to kill it from the processes list.
** Tags added: amd64 oneiric
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-system-monitor (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
This is also cropping up on ubuntu 11.10 beta 1 - 64 bit, though not all
the time. I first noticed this a few weeks ago, when all the other
windows closed as soon as i hit X, except for the system monitor which
behaves erratically - this problem has never happened to me in Natty,
Maverick or
Same for me (Natty 64bit).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/482680
Title:
System Monitor won't close through normal methods, I have to kill the
process.
--
desktop-bugs mailing
I can confirm this in Natty too. On x86. I have to open a bash shell and
kill the process.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/482680
Title:
System Monitor won't close through normal
I can confirm this on Ubuntu 10.10 amd64.
Gnome system monitor won't close with the menu quit or window icon quit button.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/482680
Title:
System
Just started happening to me as well, adding this comment because it
only began after I installed Rubyripper.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/482680
Title:
System Monitor won't
I also have this problem on 10.10 maverick meerkat.
I was ripping an audio cd with rubyripper and wanted to see if rubyripper
actually used multiple threads (I'd set it to 3, and I have a quadcore cpu) but
then I couldn't close the System Monitor window anymore.
When rubyripper was finished, I
Hi everybody.
I had experienced the same issue with system monitor until today. But now GSM
closes quite well again. The only change that I can remember is that I've
deleted System monitor applet from the bottom panel. I tried add the applet
back to panel but GSM keeps quiting OK by any mean -
Happening to me too. It seems to be happening since the latest update
round, although gnome-system-monitor wasn't updated then. The version of
gnome-system-monitor I have installed is 2.28.0-0ubuntu1.
On my system too it does not happen all the time. The first time I tried
running it with strace
Hi, this just started happening to me as well.
--
System Monitor won't close through normal methods, I have to kill the process.
https://bugs.launchpad.net/bugs/482680
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
I, too, am experiencing this problem. The process is also using a
consistently high amount of CPU (36-42%), as is dbus-daemon; I suspect
that the two things are related.
--
System Monitor won't close through normal methods, I have to kill the process.
https://bugs.launchpad.net/bugs/482680
You
I just tried installing the debug symbols for gnome-system-monitor as
per the linked instructions. However, the instructions aren't fully
clear.
Although the installation went OK, running gnome-system-monitor-dbgsym
results in this:
dar...@ubuntu-desktop:~$ gnome-system-monitor-dbgsym
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
Hi Sebastien,
Presumably you'd only be interested in a backtrace when I'm experiencing
this problem. Can you confirm?
Thanks.
--
System Monitor won't close through normal methods, I have to kill the process.
https://bugs.launchpad.net/bugs/482680
You received this bug notification because you
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35687056/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/35687057/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/35687058/ProcStatus.txt
** Attachment
24 matches
Mail list logo