Public bug reported:
TL;DR: Double-check the indexing of radio buttons in the Additional
Drivers dialog and how they correspond to installation actions, because
there's something fishy going on.
I have a Radeon HD 6870, and on a fresh 13.04 install I wanted to
install proprietary drivers for it.
There seem to possibly be several different issues going on here, but
I'll tell you how I worked around one of them. My symptoms were: Banshee
is playing music, monitor goes off due to machine idle, Banshee
continues playing until end of track and then stops. When I move the
mouse to get the
I lost a video card over the weekend, so unfortunately I can't test the
proposed fix of disabling and re-enabling the Animations plugin.
However, I can provide my CCSM configuration related to the Animations
plugin, which I've attached. It was generated with `gconftool-2 -R
I'm on Oneiric with all the -proposed updates, and I've been seeing this
issue for a month or longer, but I don't use any apps that do HTML5
notifications. The main time I seem to see these white boxes pop up is
when clicking links from another app (e.g. pidgin, hotot) that open in
chrome. Also
One more thing: I'll second the observation that the size of the white
box seems related to the size of the window being opened. Others have
reported that, when the box is caused by an HTML5 notification, it is
the same size as that notification's normal window. When I see white
boxes pop up after
I see this behavior as well under Unity, even with global menus disabled
(i.e. I uninstalled indicator-appmenu). Even with the profile setting
Show menubar by default in new terminals unchecked, when I launch a
new gnome-terminal, the menubar is displayed. As Victor described, the
Show menubar
There is also discussion of indicator-multiload as the source of the
memory leak in #720446. Look in particular at comments #42 and #44
there. These say that: 1) the leak does not occur when using indicator-
multiload in Classic, only in Unity; and 2) indicator-multi-load is,
every second, loading
@Robotex: Yes, that's true, but it misses the point I was trying to
make. There is the system indicator applet (which lives in the gnome
panel) that *looks* just like indicator-multiload (which lives in the
indicator area), and I agree that these are different programs with
different codebases.
With Michael's patch I've had Unity running with indicator-multiload for
almost 20 minutes now with no noticeable memory leak. Looks like you got
it, Michael. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Over in #779717 (comment #18), Michael Hofmann has a patch for Unity
that seems to fix the memory leak that is so noticeable when indicator-
multiload is running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Over in #779717 (comment #18), Michael Hofmann has a patch for Unity
that seems to fix the memory leak that is so noticeable when indicator-
multiload or system load indicator are running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Since upgrading to Natty (non-unity mode), I have also experienced the
problem Stephen described (can only make another edge flip after
focusing a window), but I just found a work-around by accident. In the
Desktop Wall plugin, Bindings tab, under Move Within Wall, I added mouse
bindings for each
I just posted a comment that might provide a workaround to this issue,
over on Bug 771448:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/771448/comments/5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Sam,
It might be worth looking at this comment I just posted on Bug 771448:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/771448/comments/5
The gist is that it seems like the edge-flip-pointer behavior described
there and the edge-flip-on-mouse-button stuff we're talking about here
I've upgraded to Karmic Alpha-2, as requested. The bug still crops up
intermittently, where an application (especially Eclipse) will hang when
I'm interacting with the GUI using the mouse. Contrary to my earlier
report, it doesn't seem to be specific to Synaptics, as I've reproduced
the bug while
I've been at a conference for the last week and had to have a stable
system, so I switched temporarily to metacity. I can say that the bug
doesn't seem to manifest itself in this case -- I've only seen it with
compiz enabled.
I've just re-enabled compiz and followed the first few steps that Geir
Public bug reported:
Binary package hint: xorg
Since the upgrade from Intrepid to Jaunty, X will hang randomly. It has
happened in Firefox (while scrolling a webpage with the touchpad),
OpenOffice (moving mouse and clicking an icon), and Eclipse several
times while interacting with UI elements
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27589267/Dependencies.txt
** Attachment added: LsHal.txt
http://launchpadlibrarian.net/27589268/LsHal.txt
** Attachment added: LsMod.txt
http://launchpadlibrarian.net/27589269/LsMod.txt
** Attachment added: LsPci.txt
** Attachment added: output of `lspci -vvnn`
http://launchpadlibrarian.net/20235288/lspci.out
--
syndaemon turns disabled touchpad back on after typing
https://bugs.launchpad.net/bugs/300523
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Further investigation of this issue has seen me return to the vanilla
Xorg.conf (without SHMConfig turned on). The issue can be described more
simply as follows.
1. syndaemon, as launched by the default Intrepid install, is using XInput to
change the touchpad properties.
2. synclient uses
Public bug reported:
When I upgraded to Ubuntu 8.10, the button on my Asus laptop that
toggled the touchpad on and off stopped working. The button is
controlled by the included /etc/acpi/asus-touchpad.sh, which uses
synclient to toggle the touchpad state. I turned on SHMConfig in my
Xorg.conf and
Thanks for the reply. It seems after the latest round of updates my
problem matches yours: wireless extensions are still there after
resume, and unloading and reloading the driver generally fixes things
and allows NM to recognize the wireless card again.
On 9/28/06, Mary Gardiner [EMAIL
22 matches
Mail list logo
