Public bug reported:
Binary package hint: gnome-system-monitor
When run in Parallels, upgraded from Hardy, Gnome System Monitor draws
incorrectly.
Positioning information seems skewed.
Screen shot enclosed.
There is a shadow window, and the main display area seems to be shrunk
vertically.
** Attachment added: sysmon.png
http://launchpadlibrarian.net/18622499/sysmon.png
--
Gnome System Monitor garbled display on Parallels
https://bugs.launchpad.net/bugs/284691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Could you point me at the bug number?
I did check the currently active bugs
--
Gnome System Monitor garbled display on Parallels
https://bugs.launchpad.net/bugs/284691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
My family is starting to hate GNU/Linux because of this bug.
It should be high priority to fix this.
I second this. It's confusing for the family because if they get
connection failure for the user that did get the network-manager, they
have no way of reconnecting it when logged in as
Ludwig, I have this in Ubuntu on Parallels with updating from 8.04.
Does anyone know how I could fix this by hand?
--
strange graphics bug, window looks squished, wrong colors (in
gnome-system-monitor, gnome-do)
https://bugs.launchpad.net/bugs/208570
You received this bug notification because
*** This bug is a duplicate of bug 208570 ***
https://bugs.launchpad.net/bugs/208570
Thanks Pedro.
--
Gnome System Monitor garbled display on Parallels
https://bugs.launchpad.net/bugs/284691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just another voice to add to this discussion which echos a fair amount
of what I have already read.
- When I upgraded to Jaunty, I noticed that the update icon did not appear.
I assumed that this was a bug introduced during the update.
- upgrade manager juat appearing on its own is a really bad
I have had no feedback unfortunately.
I would have thought that it was standard practice to record the bug that this
is supposed to be a duplicate of, otherwise we're no wiser. :(
I have checked over the currently pending bugs and I see nothing similar.
Either Pedro is mistaken or the related bug
Some discussion on this issue at the SANE project is here:
https://gitlab.com/sane-project/backends/-/issues/472
** Bug watch added: gitlab.com/sane-project/backends/-/issues #472
https://gitlab.com/sane-project/backends/-/issues/472
--
You received this bug notification because you are a
