Bug 15659 - xfwm gives incorrect description of setting affecting focus of mouse (see comments 3, 4)
Summary: xfwm gives incorrect description of setting affecting focus of mouse (see com...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Jani Välimaa
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-08 21:38 CEST by andré blais
Modified: 2015-10-27 06:56 CET (History)
0 users

See Also:
Source RPM: xfwm4-4.11.0-2.mga4.src.rpm
CVE:
Status comment:


Attachments

Description andré blais 2015-04-08 21:38:43 CEST
Description of problem:

In the xfwm configuration,
under the focus tab,
there is the option to click to focus, or alternately for focus to follow mouse.

When click to focus is selected, and one scrolls outside the focus area,
the focus changes to the area scrolled.
On other desktops, as well as other versions of xfwm, scrolling outside the focus area does not change the focus.  One must click.

In the xfconf editor, the parametre in question is
xfwm4/general/click_to_focus  boolean


Steps to Reproduce:
1. Change the focus option to click-to-focus
2. Click to focus in one window
3. Scroll in another window, without clicking
4. The focus changes to the scrolled window.

Set severity to major as it can lead to loss of data, since it is not immediately apparent that the focus has changed, and one often types in the wrong window.
As well, it causes a considerable waste of time.

Reproducible: 

Steps to Reproduce:
David Walser 2015-04-09 00:04:14 CEST

Assignee: bugsquad => jani.valimaa

Comment 1 Jani Välimaa 2015-04-09 07:31:08 CEST
I don't have any mga4 machine near, but at least in mga5 you can change the behavior via xfwm4-tweak-settings: Accessibility tab -> Uncheck the "Raise windows when any mouse button is pressed" option.
Comment 2 Jani Välimaa 2015-04-09 07:34:53 CEST
(In reply to Jani Välimaa from comment #1)
> I don't have any mga4 machine near, but at least in mga5 you can change the
> behavior via xfwm4-tweak-settings: Accessibility tab -> Uncheck the "Raise
> windows when any mouse button is pressed" option.

I typoed the tool name.. it's xfwm4-tweaks-settings.
Comment 3 Jani Välimaa 2015-04-09 10:34:08 CEST
Got some feedback about this @IRC:

'that setting in xfwm4-tweaks should read "Focues windows when any mouse button is pressed", if it raises the window as well depends on "Automatically raise windows when they receive focus" and "Raise window when clicking inside application window"'.

The other two mentioned settings can be found from "Focus" tab in xfwm4-settings.
Comment 4 andré blais 2015-04-09 13:18:23 CEST
(In reply to Jani Välimaa from comment #3)
> Got some feedback about this @IRC:
> 
> 'that setting in xfwm4-tweaks should read "Focues windows when any mouse
> button is pressed", if it raises the window as well depends on
> "Automatically raise windows when they receive focus" and "Raise window when
> clicking inside application window"'.
> 
> The other two mentioned settings can be found from "Focus" tab in
> xfwm4-settings.

I found the problem, from your suggestion.
There is a setting in the xfconf editor under xfwm4 / general,
called "raise_with_any_button"
It is checked by default.  (I hadn't changed it.)
When unchecked, scrolling with the mouse wheel no longer steals focus.
So that setting should be called "change focus with any button or mouse wheel", to be clear.
And yes, that is the same setting that you referred to under
"xfwm4-tweaks-settings", accessibility tab,
"Raise windows when any mouse button is pressed"

It should also be called "change focus with any button or mouse wheel".
As I noted in the initial description, there is already a setting in
"window manager"/focus to "click to focus" (instead of following mouse pointer).

So this bug becomes an incorrect description of the setting.
Comment 5 Jani Välimaa 2015-04-09 13:23:56 CEST
If you think the descriptions for some settings are not clear, you should file a bug to upstream.
Comment 6 andré blais 2015-04-09 13:29:33 CEST
Changed summary to reflect real problem.
Note also that the default is incorrect, it should be unset by default.

OK, I'll report it upstream.

Summary: xfwm does not respect configuration for focus of mouse => xfwm gives incorrect description of setting affecting focus of mouse (see comments 3, 4)

Comment 7 Jani Välimaa 2015-04-09 13:34:30 CEST
I'll check later which is the upstream default setting for this. Another story is who decides which should be the default setting. You, we (as Mageia), upstream or other window manager upstreams.
Comment 8 Jani Välimaa 2015-04-09 15:30:42 CEST
Upstream's default for raise_with_any_button is true/enabled [1].

[1] http://git.xfce.org/xfce/xfwm4/tree/defaults/defaults#n37
Comment 9 andré blais 2015-04-09 20:40:13 CEST
(In reply to Jani Välimaa from comment #8)
> Upstream's default for raise_with_any_button is true/enabled [1].
> 
> [1] http://git.xfce.org/xfce/xfwm4/tree/defaults/defaults#n37

That confirms that it wasn't changed accidentally in my recent clean install.

I would suspect the faulty description is at least partly responsible.
In any case, I have never encountered that behavior in any other graphic environment.  Not even older versions of xfce.
So I would favour changing it in Mageia if upstream doesn't fix it, to avoid grief for other xfce users.
I'll post the upstream bug report number here when done.  (Later today)
Comment 10 andré blais 2015-04-10 07:49:19 CEST
OK, reported upstream https://bugzilla.xfce.org/show_bug.cgi?id=11811

I changed the suggested description to "Change focus on movement of mouse wheel",
since that is all the option adds, and only if the focus-on-click option is set.

If focus-on-click is unset (meaning focus on mouse location),
then the option in question has no effect.

I also requested unsetting the option by default.
Jani Välimaa 2015-04-10 15:30:46 CEST

See Also: (none) => https://bugzilla.xfce.org/show_bug.cgi?id=11811

Comment 11 Jani Välimaa 2015-04-10 15:32:51 CEST
Thx for reporting this to upstream. CC'ed also to upstream report.
Comment 12 andré blais 2015-04-10 19:10:18 CEST
Thanks for your help figuring out the problem.
It was an aggravating few weeks before the solution.
Comment 13 Samuel Verschelde 2015-09-21 13:18:34 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 14 Marja Van Waes 2015-10-27 06:56:01 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.