PDA

View Full Version : [SOLVED] Grab handles look odd on some windows



lifelike27
May 20th, 2011, 01:11 AM
Does anyone else have this problem? http://ubuntuone.com/p/uRp/

It's fine for the terminal and nautilus: http://ubuntuone.com/p/uRq/

There are ways of 'hiding' it as shown here (http://www.omgubuntu.co.uk/2011/05/disable-the-resize-grip-in-ubuntu-11-04/), but I wanted to fix this bug rather than hide it.

lifelike27
May 22nd, 2011, 06:45 AM
Is no one replying because it's a stupid question (i.e it's mentioned somewhere else I haven't looked that this is a known, unsolvable issue) or just bad luck?

Larkspur
May 22nd, 2011, 03:43 PM
Well, the solution you linked to seems to be the best way to resolve it. According to the thread (http://askubuntu.com/questions/29209/disable-resize-gripper-in-windows) omgubuntu seem to have got the fix from, applying that for all themes (without editing the .gtkrc files) could involve recompiling gtk itself.

lifelike27
May 22nd, 2011, 08:53 PM
So I added that code to the file and it's taken off the grab handles for all other windows except chrome, which was the original reason I wanted to remove them...

Larkspur
May 22nd, 2011, 10:18 PM
So I added that code to the file and it's taken off the grab handles for all other windows except chrome, which was the original reason I wanted to remove them...

Have you got Chrome using its default theme or have you chosen the option for gtk intergration (or whatever it is - it's been a while since I've used Chrome)?

lifelike27
May 22nd, 2011, 10:24 PM
Yup, it also appears with the Chrome 'classic' theme as well, except it's blue then.

Larkspur
May 22nd, 2011, 11:07 PM
Have you logged out at any time? Sometimes, that's all it takes for a new theme to be fully applied. It's not likely in this case, sadly; Chromium (http://code.google.com/p/chromium/issues/detail?id=75048) and a whole load of other apps (https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/704105) are affected, and it seems no one has come up with a fix yet.

lifelike27
May 24th, 2011, 02:07 PM
Shame. It looks odd. =\

lifelike27
June 5th, 2011, 08:41 PM
This problem is solved in Chrome Unstable (v13).

Will just have to wait for the stable release then.