[Ubuntu-x-swat] [Bug 1272338] Re: Xorg memory leak on trusty
Oddly I can sit here and click between windows, changing the highlighting/focus, and watch memory bump up a 5-10mb each time, and NOT get reclaimed. Toggling compositing on and off does not relinquish the memory, I wonder if disabling the compositing layer will all together, but seems related to the desktop effects on windows. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1272338 Title: Xorg memory leak on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-driver/+bug/1272338/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1272338] Re: Xorg memory leak on trusty
I'm getting this now in kde after upgrading 14.04 kernel to 3.16 and the beta fglrx drivers to run it. Not sure if also at the time changing the desktop effects opengl render modes affected this (compositing==ogl3.1, qt graphics==native, scaling==accurate, vsync==auto). Took about 8 hours to climb to consuming 28gb of ram. :\ $ xrandr Screen 0: minimum 320 x 200, current 9600 x 1200, maximum 16384 x 16384 (5x 1920x1200 displays in eyefinity) $ plasma-desktop -v Qt: 4.8.6 KDE Development Platform: 4.13.3 Plasma Desktop Shell: 4.11.11 $ uname -a Linux host 3.16.7-031607-generic #201412010535 SMP Mon Dec 1 10:36:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ sudo dpkg -l | grep fglrx ii fglrx-amdcccle-updates2:15.200-0ubuntu0.3 amd64Catalyst Control Center for the AMD graphics accelerators rc fglrx-core2:15.200-0ubuntu0.3 amd64Minimal video driver for the AMD graphics accelerators ii fglrx-updates 2:15.200-0ubuntu0.3 amd64Video driver for the AMD graphics accelerators ii fglrx-updates-core2:15.200-0ubuntu0.3 amd64Minimal video driver for the AMD graphics accelerators ii xvba-va-driver0.7.8-1ubuntu3 amd64XvBA-based backend for VA API (AMD fglrx implementation) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1272338 Title: Xorg memory leak on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-driver/+bug/1272338/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 993655] Re: Unity looses mouse click handler when using enabling USB headset
I'd spent the weekend dealing with this as last week someone at work gave me one of these plantronics devices to use, and I was stoked it would act as a headset for my pc as well. Then I started getting the screen freeze issue, and never figured out it was linked to the stupid headset. After upgrading from 12.04 to 13.10 (hitting a ton of ubuntu bugs along with the way with the intel 4000 video chipset, forcing me to hit 13.10 until I got a stable system again), and trying every window manager out there, still had this issue... Seemingly after doing anything that triggered the sound device, finally figured out it was related when disconnecting the plantronics headset would allow me to click on my display windows again. Argh! If nothing else, can you (Canonical) simply blacklist the device by default, or at least add the xorg entry if you can't find a better way of dealing with it? This is likely to make any user lose their hair as it about did for me. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/993655 Title: Unity looses mouse click handler when using enabling USB headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/993655/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 413168] Re: Karmic upgrade not shutting off backlight after time
There does seem to be a conflict between gnome-power-manager and gnome- screensaver in relation to the idle timers. Using one or the other they behave, but not when together. Forcing install of older Jaunty packages works fine, so I don't believe this is an xorg issue, but something rather with one or the other gpm or screensaver packages. I updated fully end of this week and didn't resolve anything with the screensaver and monitor dim, so I went back to using the old jaunty packages. Doing a system update only made my suspend broken, network manager behave erratically, and introduced other broken application behavior, so karmic still seems to be quite unstable. Ugh. -- Karmic upgrade not shutting off backlight after time https://bugs.launchpad.net/bugs/413168 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
