← Back to team overview

ubuntu-gnome-qa team mailing list archive

Re: [Ubuntugnome-qa] CFT: big GNOME update!

 

On 12/20/2014 10:27 PM, Tim wrote:
> On 21/12/14 00:58, Bruce Pieterse wrote:
>> On 12/20/2014 09:06 AM, Tim wrote:
>>> Hey All,
>>>   We will be landing a big update into vivid early next week which is now staged on ppa:ubuntu-gnome-packaging/core3.14. Please test and let us
>>> know of any issues you might find. Needs to be installed over a clean vivid system or all gnome3-team ppa's purged first.
>>>
>>> Thanks
>>>    Tim
>>>
>> Hi Tim,
>>
>> I have upgraded to this PPA. Only problem I could find was
>> adwaita-icon-theme was not installed along with the upgrade and as such
>> the following occurred:
> This is fixed, but the upload got stuck, added to the ppa for now.
>> - Mouse cursor disappears when hovering over activities and dash making
>> it hard to open a application
>> - In gnome-tweak-tool Cursor theme is disabled and has nothing set
>> - Changing a drop-down option renders a image icon where the drop-down
>> arrows are supposed to be
>>
>> Easy way to reproduce the above is to remove adwaitia-icon-theme and
>> restart the shell (CTRL+F2) if it is installed already.
>>
>> Additionally, focus mode "Click" does not put focus on windows any more.
>> You have to click the titlebar in order to get focus on a window which
>> is very different behaviour in current 14.10 and 15.04 prior to using
>> this ppa.
> I'm not sure what you mean here?
I figured out why window focusing doesn't occur properly last night.
Basically keyboard input is redirected to the last focused app and if I
select an input field on a non-focused window app, I'll be typing in the
non-focused app instead of the focused app (although it isn't focused
yet, but mouse interaction works). The only way to achieve focus and be
able to type in the the input field is by clicking on the header/title
bar to gain focus.

Essentially the settings to reproduce this is that Focus Mode needs to
be set to Click and Window Action Key needs to be set to Disabled. So
far, I have only tested this on two different machines (1 VM and 1 real)
and was able to reproduce this both using main and staging ppa's.

I would like to file a bug for this but not sure against which package.
I'll also test vivid and 14.04 to see if this occurs as well.

Thanks
>> Please let me know which packages to file a bug against for these two
>> problems above.
>>
>> Thanks
>>
>

-- 
All the best,

Bruce

FSF Member 10674 / The FSF is a charity with a worldwide mission to advance software freedom / Join the Free Software Foundation: http://www.fsf.org/register_form?referrer=10674




Follow ups

References