Description of problem: At last, I got that very fine tuned bug: It is impossible to click on the userdrake tab "Groups" but only under fvwm2 window manager. This is an oxygen-gtk bug because if I install another theme, as adwaita and do GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc userdrake under fvwm2, everything works fine again. How reproducible: all the time Steps to Reproduce: 1. login into fvwm 2. open userdrake, either from MCC, or commandlie 3. try to click on the tab named "Groups" Cheers, Chris.
Hi, thanks for reporting this bug. Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedCC: (none) => juan.baptiste, thierry.vignaudBlocks: (none) => 4300
you confirm that you cannot reproduce with other window managers ? metacity ? kwin ? I here, cannot reproduce with kwin. Hugo (oxygen dev)
CC: (none) => hugo
Questions: 1/ can you double check whether this could be a duplicate of "https://bugs.kde.org/show_bug.cgi?id=293967" 2/ does disabling the option "drag windows from all empty areas" from "oxygen-settings" (or oxygen kde style options) fix the issue ?
ok. I am able to reproduce, only with fvwm2, and not metacity, nor oxygen-gtk. Indeed, disabling the "drag from all empty areas" fixes it.
meant: "nor kwin"
Hi There, thanks for the link, that was intructive. Actually, I am the maintainer of fvwm2 and it seems to be indeed linked to the way oxygen-gtk handles mouse events when clicking on windows that competes with the window-manager. The drag window options did not change anything, which is weird, because even specifying that I want drag from title bar only still allowed me to drag from inside "userdrake window". It seems to be indeed the origin of the pb because that something already specified in the window-manager. Looking into the fvwm2 configuration file, I found a way to fix the bug by asking fvwm2 to not consider any action by a mouse click inside a window application. Then the tabs work again. I'll push the fix onto fvwm2, which closes the bug I guess. But I really don't know if this should be called an oxygen-gtk "feature", or "bug". Cheers, Chris.
Opss, sorry, I missed you last post. I did not push anything yet on fvwm2, so let me know if you want to fix this on oxygen or fvwm2. Cheers.
@chris. Don't push yet :) I "think" I can fix it in oxygen (within a day). If not, your fix is fine. I believe it "disables" the 'drag windows from all empty areas" 'feature' of oxygen alltogether, and therefore the bugs that come with it :) Will keep you posted.
concerning the setting not being respected, I had the same issue. Since userdrake must run as root (or sudo) I had to change the "root" settings (using sudo oxygen-settings, or su; oxygen-settings) Then I could disable the window drag for oxygen and then userdrake work. Anyway, I think I have a working fix now :)
ok Fixed in http://quickgit.kde.org/?p=oxygen-gtk.git&a=commit&h=ce1070182965133217a1ed17243b220f2b7b0797 Someone should double check and close. There will be a new release of oxygen-gtk2 in a couple of days.
Cool, thanks a lot!
Hugo: time to do a beta1 prerelease we could package & test in cauldron?
Please test new oxygen rpm.
CC: (none) => dmorganec
*** Bug 4271 has been marked as a duplicate of this bug. ***
CC: (none) => richard.j.walker
CC: (none) => ennael1Blocks: 4300 => 5034
Sorry, forgot to check, this is fixed for me now under fvwm2! you can close. Cheers, Chris.
ok thanks
Status: NEW => RESOLVEDResolution: (none) => FIXED